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've inherited an mkdocs-material project which uses LunrJS for the search and I'm new to Lunr.
I see Lunr has various search operators such as wildcards, fields, etc. One of these would be colon (:) for field search.
My question is whether there is a way to disable this color(:) operator or customize the operators in general.
For example, we have "ERROR: This error ..." in our documentation. If the user searches for "ERROR This" it is found, but if the user searches for "ERROR: This" it will NOT be found. I'd like to gain more control over these operators and the separators.
I can see where I can customize the separators with "lunr.tokenizer.separator = new RegExp(...)", but what about disabling, adding, or customizing operators?
Thank you for your help.
The text was updated successfully, but these errors were encountered:
I've inherited an mkdocs-material project which uses LunrJS for the search and I'm new to Lunr.
I see Lunr has various search operators such as wildcards, fields, etc. One of these would be colon (:) for field search.
My question is whether there is a way to disable this color(:) operator or customize the operators in general.
For example, we have "ERROR: This error ..." in our documentation. If the user searches for "ERROR This" it is found, but if the user searches for "ERROR: This" it will NOT be found. I'd like to gain more control over these operators and the separators.
I can see where I can customize the separators with "lunr.tokenizer.separator = new RegExp(...)", but what about disabling, adding, or customizing operators?
Thank you for your help.
The text was updated successfully, but these errors were encountered: