chore: Generalized Search - implement simple query, refactor queries [CHI-3004] #760
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR
content
(case, case section, contact, transcript) to use the above. This approach is more resilient to direct user input while also simplifies the code used to generate queries, at the expense of loosing some custom weights we introduced when originally implemented.The reason for this change is to prevent bugs being thrown by our ElasticSearch services when users introduced special characters. Another option (for historical purposes) was to escape the special characters, but that feels like a more fragile approach. See #759.
Checklist
Verification steps
AFTER YOU MERGE
You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P