feat: support expired and not-found ref API errors #327
+113
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Types of changes
Description
This PR adds support for two new ref-related errors that may be returned by Rest API V2:
RefNotFoundError
: Thrown when a query's ref does not exist.RefExpiredError
: Thrown when a query's ref is expired (generally older than 5 minutes if it is not the master ref or a release).This is a non-breaking change since the errors were previously thrown as
ForbiddenError
s. The new error types extend fromForbiddenError
and will continue to work withinstanceof ForbiddenError
.The new errors will extend from
PrismicError
in a future major version for better semantics.Checklist:
🫎