CorpseFinder: Remove impossible exclusion actions for corpse content items - #487
Merged
Conversation
In some cases we removed more results than necessary and in other cases we didn't remove enough (parents of nested exclusion targets).
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.
Corpses that have content items are always folders.
If we create exclusions for content items, we must always exclude the top level item, i.e. the root corpse itself -> removing the whole entry.
So excluding a content item is always the same as excluding the whole corpse.
So to reduce confusion here, I removed the exclusion context option for content items.