Open
Conversation
- Grammar now allows for unquoted single word queries - Special characters are allowed only in quoted queries - Update tests to reflect this
nonword
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR addresses issues in SCC-5296 and SCC-5298, and makes extensive use of AI assistance.
Some modifications to the grammar:
titleorauthor, operators likeANDorNOT, relation terms likeanyorall) case insensitiveFix bug where
displayParsedwas returning text backwardsFix bug where top-level query for cql queries was
shouldinstead ofmust, which allowed spurious matches whenever filters were appliedAdd a
CqlQueryclass so we can use the same AST forbuildEsQueryanddisplayParsedand not parse twiceRequire date format to pass validation
Include items with cql results
Fix/Update/Add tests