Remove some more usages of ParseFieldMatcher #22398
Merged
Conversation
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
nik9000
approved these changes
Jan 1, 2017
…MatchQueryBuilder
javanna
force-pushed
the
enhancement/remove_parse_field_matcher_usages_3
branch
from
b5bc81b to
e5f1597
Compare
javanna
force-pushed
the
enhancement/remove_parse_field_matcher_usages_3
branch
from
e5f1597 to
57cfe07
Compare
|
retest this please |
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 is yet another step on the way of removing ParseFieldMatcher. It contains mostly mechanical removals of ParseFieldMatcher arguments from parse methods.
Relates to #19552
Relates to #22130