fix(eap-resolver): escape sequences should also be translated in a in query#104188
Merged
DominikB2014 merged 5 commits intomasterfrom Dec 2, 2025
Conversation
github-actions
bot
added
the
Scope: Backend
DominikB2014
changed the title
in query
wmak
approved these changes
Dec 1, 2025
Member
wmak
left a comment
wmak
left a comment
There was a problem hiding this comment.
Can you add a test for arrays with numbers too? otherwise lgtm
DominikB2014
deleted the
dominikbuszowiecki/browse-164-truncated-queries-affect-filtering-on-query-summary
branch
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
Resolves BROWSE-164
If you use a
inquery with escaped characters, we should also translate them for the elements in the array, the same as we do for a regularisquery. This is so we never have discrepancies between the results of queriesattribute:[a]andattribute:a