v5.0.0
BREAKING CHANGES
-
When a field could not be found, the message on the
thrown error looked like this[github-project] "NOPE" could not be matched with any of the existing
field names: "Title", "Assignees", "Status", "Labels", "Linked pull
requests", "Reviewers", "Repository", "Milestone", "Text", "Number",
"Date", "Single select", "Iteration". If the field should be considered
optional, then set it to "nope: { name: "NOPE", optional: true}it is now
Project field cannot be found
The original message can still be retrieved using
error.toHumanMessage() -
When a user value cannot be matched with a field
option, the message on the thrown error looked like this[github-project] "unknown" is an invalid option for "Single select"
it is now
Project field option cannot be found
The original message can still be retrieved using
error.toHumanMessage() -
if a user tried to update a read-only field, the
message on the thrown error looked like this[github-project] Cannot update read-only fields: "Assignees"
(.assignees)it is now
Project read-only field cannot be updated
Features
GitHubProjectErrorGitHubProjectUnknownFieldErrorGitHubProjectUnknownFieldOptionErrorGitHubProjectUpdateReadOnlyFieldError