This repository was archived by the owner on Jan 23, 2026. It is now read-only.
feat: add support for .throwOnError() #250
Merged
Conversation
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
maxmetcalfe
changed the title
🚀 Preview Release Statusfalse Last updated: 2025-09-08T08:48:00Z |
Contributor
|
@maxmetcalfe thank you for this PR! Can you please add a few more test cases? |
Contributor
Author
|
@mandarini - added more tests! |
mandarini
approved these changes
Sep 8, 2025
Contributor
mandarini
left a comment
mandarini
left a comment
There was a problem hiding this comment.
Approving this. Thank you @maxmetcalfe . Eventually, the goal is to add this functionality to all the client libs. Will be easier once moved to the monorepo, in a shared lib.
Member
|
🎉 This PR is included in version 2.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
What kind of change does this PR introduce?
Adds support for
.throwOnError()(see: #150, supabase/supabase-js#92)What is the current behavior?
Errors are not thrown and instead a response object is returned with
dataanderrorproperties.What is the new behavior?
When
.throwOnError()is supplied, errors are thrown.Additional context
This is disabled by default as it's a breaking change. This follows the identical function added in supabase/postgrest-js#188.