You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to see if we've defined or used the term facet anywhere.
What did you expect?
The search results would only be those pages containing the exact term specified.
What did you see instead?
Multiple pages containing the term fact; no pages that contain the term facet.
Solution
We should enable Algolia's "advanced syntax" option in the JS that makes the client-side query from /search/: https://www.algolia.com/doc/api-reference/api-parameters/advancedSyntax/#how-to-use. We should probably not enable it on the index by default, in case there are unintended side effects -- and in order to let this be tested in isolation, in a CL preview context.
This appears to fix #2875 as well, given the contents of the Algolia reference doc:
Phrase query: a specific sequence of terms that must be matched next to one another. A phrase query needs to be surrounded by double quotes (").
Note: Typo tolerance is disabled inside the phrase (i.e. within the quotes).
The text was updated successfully, but these errors were encountered:
What page were you looking at?
https://cuelang.org/search/?q=%22facet%22
What version of the site were you looking at?
cue-lang/cuelang.org@cfcc8af
What did you do?
I tried to see if we've defined or used the term
facet
anywhere.What did you expect?
The search results would only be those pages containing the exact term specified.
What did you see instead?
Multiple pages containing the term
fact
; no pages that contain the termfacet
.Solution
We should enable Algolia's "advanced syntax" option in the JS that makes the client-side query from
/search/
: https://www.algolia.com/doc/api-reference/api-parameters/advancedSyntax/#how-to-use. We should probably not enable it on the index by default, in case there are unintended side effects -- and in order to let this be tested in isolation, in a CL preview context.This appears to fix #2875 as well, given the contents of the Algolia reference doc:
The text was updated successfully, but these errors were encountered: