This repository was archived by the owner on Oct 9, 2025. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 174
Allow to pass fetch options while building the query #527
Closed
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
g12i
commented
Mar 23, 2024
Instead of this being Next.js specific, not sure if it might be better to just allow customization of any |
Yeah, I agree @bnjmnt4n. Let me make a quick update |
Hello @soedirgo, any chance this gets reviewed? |
@soedirgo bump :P |
Any update on this? |
Hi @g12i ! Thank you very much for you meaningful contribution, and apologies for not reviewing it for such a long time. This repository is deprecated and has moved to the new Supabase JS monorepo. May I ask you, if you believe this change is still needed, please open a new PR in the monorepo and include a link back to this thread for context:
I will be closing this PR now, but you can always access it and view the changes, even after the repo is archived, don't worry! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
This adds a possibility to pass any fetch options (e.g.
next
options to fetch while building the query.What is the current behavior?
Currently we can pass fetch at
PostgrestBuilder
creation. Which effectively means once, if using Supabase. One would have to parse URL and alter options depending on the URL. E.g. for passingnext.tags
optionsWhat is the new behavior?
Allow to pass
fetchOptions
options when building query. The idea here isBecause FetchOptions include
signal
, it is marked as deprecated and uses.fetchOptions
internally.