Repository navigation
fix(postgrest): overwrite duplicate pagination parameters - #1620
Closed
Akishore407 wants to merge 1 commit into
Closed
Akishore407 wants to merge 1 commit into
Akishore407 wants to merge 1 commit into
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
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.
Fixes #1617.
Calling
limit(),offset(), orrange()multiple times previously added duplicate query parameters instead of replacing the previous value.This change uses
set()instead ofadd()for pagination parameters so that the latest call takes precedence.Changes
limit()to overwrite existing limit parameters.offset()to overwrite existing offset parameters.range()to overwrite existing offset and limit parameters.Testing
uv run ruff checkuv run ruff format --check