Fix derived type filtering - #4037
Open
SychicBoy wants to merge 1 commit into
Open
Conversation
Treat visible derived-type entries as filter matches instead of recursively filtering their lazy children.
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
1 participant
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.
Fixes #4028
Problem
DerivedTypesEntryNode.Filter()returnsRecursefor visible entries, causing the filter cascade to recursively filter their lazy children. This can hide derived-type entries and modify the child collection during visibility updates.Solution
MatchfromDerivedTypesEntryNode.Filter()for visible entries so their children remain lazy until the entry is expanded.