-
Notifications
You must be signed in to change notification settings - Fork 264
Review filters guide #1902
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
Comments
Merged
Another related issue: #1850 |
Merged
bors bot
added a commit
that referenced
this issue
Feb 16, 2023
2061: review filtering guide r=maryamsulemani97 a=maryamsulemani97 closes #1902, #860, #837, and #1850 - moves all operators to a new heading - removes SQL syntax and combines it with the curl code samples - replaces amazon and imdb images for facets with meilisearch demo images - removes unused images in `.vuepress/public/faceted-search` - remove redundant code samples <hr> - Improve coherence between dataset and examples - A sample document was added as part of #2050 with `rating` and `director` fields - This PR uses `movie_ratings` instead of `movies` to clarify that this is a separate dataset - `faceted_search_facets_1` still uses `movies` as this code sample is used in the API reference as well Co-authored-by: Maryam Sulemani <[email protected]> Co-authored-by: Maryam <[email protected]> Co-authored-by: maryamsulemani97 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This guide was written about a year ago and is starting to show its age. We should review it completely and possibly rewrite a few sections.
Filter expressions and operators
One major pain point is the list of filter operators, which no longer comfortably accommodates the growing number of operators (started with 3, now 6, will probably be further expanded soon). Additionally, the complexity of these operators has grown significantly and fitting everything (explanation, edge cases, comprehensive examples) in a single list item has become awkward.
Content to add
NOT
andEXISTS
EXISTS
can be negated both asattribute NOT EXISTS
andNOT attribute EXISTS
.NOT
andEXISTS
: https://meilisearch.slack.com/archives/C02DGTH89NE/p1664207880764789 (private link)NOT
andEXISTS
: https://github.com/meilisearch/documentation/pull/1869/files#r974129044IN
andOR
At the moment,
IN
works a bit like syntactic sugar for multipleOR
statements. The implementation is actually different, however, and devs do not offer any assurances the behaviour of both operators will always match.IN
andOR
: https://github.com/meilisearch/documentation/pull/1869/files#r974130580The text was updated successfully, but these errors were encountered: