-
Notifications
You must be signed in to change notification settings - Fork 102
Add filterableAttributes syntax API to settings #730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kumarUjjawal
wants to merge
5
commits into
meilisearch:main
Choose a base branch
from
kumarUjjawal:feat/attributes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b926f13
Add filterableAttributes syntax API to settings
kumarUjjawal 873f112
Fixed code samples for fileterable attributes
kumarUjjawal 89f6c6b
Added more tests for filterableAttribute
kumarUjjawal b1bd536
Merge branch 'main' into feat/attributes
kumarUjjawal afabcf1
Merge branch 'main' into feat/attributes
kumarUjjawal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify migration path for breaking change to filterable_attributes field.
The type change from
Option<Vec<String>>toOption<Vec<FilterableAttribute>>is a breaking change for code that directly accessesSettings.filterable_attributes. While the builder methods maintain backward compatibility, users who constructSettingsvia struct literals or access the field directly will need to update their code.Consider:
Run the following script to identify potential usage patterns in the codebase:
🏁 Script executed:
Length of output: 0
Length of output: 11128
Breaking change confirmed: direct field access to
filterable_attributeswill require updates.Direct field access exists in the codebase (e.g.,
documents.rslines 754, 760 accessfilterable_attributesdirectly). Code that constructsSettingsvia struct literals or directly accesses the field must be updated to work withVec<FilterableAttribute>instead ofVec<String>.The builder methods (
with_filterable_attributes(),set_filterable_attributes()) maintain backward compatibility and continue accepting strings, so most typical usage patterns are unaffected. However, any code iterating over the field or relying onStringmethods will break. Consider documenting this as a breaking change in the migration guide.