.Net: Remove legacy filtering from MEVD providers#13636
Draft
roji wants to merge 1 commit intomicrosoft:mainfrom
Draft
.Net: Remove legacy filtering from MEVD providers#13636roji wants to merge 1 commit intomicrosoft:mainfrom
roji wants to merge 1 commit intomicrosoft:mainfrom
Conversation
b764d98 to
90c71ba
Compare
90c71ba to
ab0aa44
Compare
ab0aa44 to
abdbad6
Compare
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
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.
Removes all legacy filtering logic from MEVD, leaving only (obsoleted) FilterClause and subclasses, which are still needed by ITextSearch (see conversation in #13384 (comment)).
As suggested by @westey-m let's do an SK release before merging this (see above).
Closes #10456
/cc @alzarei