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
It would be nice to let users ability to override COMPLEX_QUERY_OPERATORS_PATTERN from query configuration.
In my case I had to spend quite a bit of time understanding why queries containing a dash are not expanded, e.g. vendor-managed is not expanded because the dash character is in COMPLEX_QUERY_OPERATORS_PATTERN .
I would like to be able to customize it from configuration instead of changing the source code.
Regards,
Yegor
The text was updated successfully, but these errors were encountered:
Hm, that's actually a really interesting problem. I disagree with the proposed solution, though; I think the COMPLEX_QUERY_OPERATORS_PATTERN should just be smarter about ignoring hyphens. In fact, the hyphen is considered a complex operator in cases like this:
super -duper
super - duper
but not this:
super-duper
So unfortunately I would need to better understand when the hyphen is part of a single token and when it's surrounded by token-breaking whitespace (or other token-breaking characters).
Just giving you the option to specify this pattern is actually not going to fix anything, because if you remove the hyphen from the regex, then we won't properly be able to detect cases where there truly are complex operators.
It would be nice to let users ability to override COMPLEX_QUERY_OPERATORS_PATTERN from query configuration.
In my case I had to spend quite a bit of time understanding why queries containing a dash are not expanded, e.g. vendor-managed is not expanded because the dash character is in COMPLEX_QUERY_OPERATORS_PATTERN .
I would like to be able to customize it from configuration instead of changing the source code.
Regards,
Yegor
The text was updated successfully, but these errors were encountered: