Alternative to custom query transform now that its unsupported >9.0.0

[flynneva]

While trying to upgrade to >9.0.0 I noticed that support for a custom query transform js method was removed

What is the alternative if we would still like this feature?
Are queries still passed through the separator regex then? (from my testing...they are not any more)

Any help / tips / advice would be greatly appreciated!

[flynneva]

For example on the mkdocs-material site if you search for test::search I'd expect it to return results about the two tokens (test and search) assuming the regex separator was applied to the query.

Instead the results are null and nothing is returned. This is the same results as what I am seeing for our site as well.

[squidfunk]

Thanks for asking! This was actually an experiment to see whether this functionality is still needed. As search has been rebuilt, the way the custom query transform was defined would not work anymore. However, we can now fully alter search behavior, so supplying a custom function via a third-party script is definitely something that we can consider re-adding.

For example on the mkdocs-material site if you search for test::search I'd expect it to return results about the two tokens (test and search) assuming the regex separator was applied to the query.

The query is now correctly lexed according to lunr.js syntax. #4884 reported something similar, which is where I'll investigate whether we can treat non-field values as text. I can't make any promises though, but custom query transforms converting : to whitespace might solve the problem at hand.

[squidfunk]

As an addendum, a look in the console: