dedup values passed to PostgrestFilterBuilder.in #517
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
steve-chavez
approved these changes
Feb 7, 2024
|
🎉 This PR is included in version 1.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Dedup values passed into PostgrestFilterBuilder.in
What is the current behavior?
Values are incorporated into the url as is when duplicate values are present.
e.g. .in([1,1,2,2,3,3]) =>
in.(1,1,2,2,3,3)The caused us to get a 414 URI too long when we passed in a long array of deduplicated values by accident. Would be nice if the library took care of this.
What is the new behavior?
Values will be deduplicated as duplicated.
e.g. .in([1,1,2,2,3,3]) =>
in.(1,2,3)