Allow to pass fetch options while building the query #527
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.