SearchableText "foo **" with a standalone wildcard causes error #362
Assignees
Labels
Comments
reebalazs
added a commit
that referenced
this issue
Jun 7, 2023
Fix the problem and make "foo **" result in the same query as "foo". Without the fix this used to cause an 500 Internal Server Error. One might argue that "foo **" is not a valid query, to start with. However it can be expected as an input, thus it should not cause a cryptic error anyway. The fix causes to yield the expected results by stripping out the standalone wildcard.
reebalazs
added a commit
that referenced
this issue
Jun 7, 2023
Fix the problem and make "foo **" result in the same query as "foo". Without the fix this used to cause an 500 Internal Server Error. One might argue that "foo **" is not a valid query, to start with. However it can be expected as an input, thus it should not cause a cryptic error anyway. The fix causes to yield the expected results by stripping out the standalone wildcard.
tisto
pushed a commit
that referenced
this issue
Jun 9, 2023
Fix the problem and make "foo **" result in the same query as "foo". Without the fix this used to cause an 500 Internal Server Error. One might argue that "foo **" is not a valid query, to start with. However it can be expected as an input, thus it should not cause a cryptic error anyway. The fix causes to yield the expected results by stripping out the standalone wildcard.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fix the problem and make "foo **" result in the same query as "foo". This currently causes an 500 Internal Server Error.
One might argue that "foo **" is not a valid query, to start with. However it can be expected as an input, thus it should not cause a cryptic error anyway. The fix should cause to yield the expected results by stripping out the standalone wildcard.
The text was updated successfully, but these errors were encountered: