Expose NotFound json errors #404
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stokarenko
force-pushed
the
expose-not-found-json-errors
branch
from
c423c41
to
3b5e965
Compare
|
Hey there @gaorlov ) Very tiny improvement please ) |
gaorlov
requested changes
Jun 2, 2023
|
1.21.1 is now live. Thanks for your work and patience! |
|
hey, thanks a lot! ) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Exposes the JSON API error if it comes as a part of NotFound response - similar to the other error classes.
Keeping the backward support for sure.