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'm getting convinced that the most common use cases for #24 would actually be covered by simple prefix and postfix searches. The syntax should follow convention: for instance, any search term followed by either * or * should turn on prefix match.
(When #30 gets fixed, it would also be useful to support forcing exact matches for those cases where the default heuristics including either prefix or postfix matches would provide too many results.)
The text was updated successfully, but these errors were encountered:
I'm getting convinced that the most common use cases for #24 would actually be covered by simple prefix and postfix searches. The syntax should follow convention: for instance, any search term followed by either
*
or*
should turn on prefix match.(When #30 gets fixed, it would also be useful to support forcing exact matches for those cases where the default heuristics including either prefix or postfix matches would provide too many results.)
The text was updated successfully, but these errors were encountered: