Repository navigation
Make wildcard conditions case-insensitive - #37
Merged
royduin merged 2 commits intoSep 30, 2026
Merged
Conversation
kevinmeijer97
approved these changes
Sep 29, 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
3 participants
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.
The
LIKE,NOT LIKE,STARTS_WITHandENDS_WITHoperators are parsed into awildcardquery on the.keywordfield, which is case-sensitive. A condition likename LIKE catdidn't match products named "Cat ...".This adds
case_insensitive: trueto these wildcard queries (supported since Elasticsearch 7.10 and in OpenSearch).LikeParsernow uses the samevaluenotation as the other wildcard parsers.Note: the query builder stores the generated query in the entry's
valueon save and reuses it when rendering. Existing query builders therefore only pick this up after the entry is re-saved or the storedvalueis removed.Also removed the
property.phpDocTypePHPStan ignore rule; it no longer matches any error with the latest PHPStan, which made the analyse workflow fail.