This repository was archived by the owner on Sep 8, 2025. It is now read-only.
feat: add max-affected and handling parameters in prefer header support#520
Open
danfimov wants to merge 2 commits intosupabase:mainfrom
Open
feat: add max-affected and handling parameters in prefer header support#520danfimov wants to merge 2 commits intosupabase:mainfrom
danfimov wants to merge 2 commits intosupabase:mainfrom
Conversation
Contributor
|
These are currently not supported in the JS client library and this library follows closely to the JS library. I'm going to leave this open until there is support for it in the JS library. |
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 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?
handlingparameter inPreferheader supportmax-affectedparameter inPreferheader supportWhat is the current behavior?
Currently support for this parameters is not implemented.
Additional context
PostgREST documentation: