fix(postgrest): throw a PostgrestException for a non-JSON 2xx body - #459
Merged
Tr00d merged 2 commits intoOct 2, 2026
Merged
Conversation
Tr00d
reviewed
Sep 30, 2026
Contributor
Author
Tr00d
approved these changes
Oct 2, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
closes #260
a 2xx body that isn't JSON, like a proxy's html error page, now throws a PostgrestException instead of a JsonException, on table queries and
Rpc<T>.on
Rpc<T>, JSON that doesn't fitTnow also throws a PostgrestException, with the JsonException inside. table queries still throw the plain JsonException for that.