fix(core): adjust how findMatchingProjects works when provided additive patterns after an exclusion to be more intuitive #19295
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.
Current Behavior
A list of patterns such as
['*', '!packages/*', 'my-package']
will not include'my-package'
as a result. This behavior feels weird though, as intuitively the patterns are parsed as:However, mechanically, we currently handle exclusions at the very end of processing patterns. This means we parse it as:
Expected Behavior
Pattern parsing is intuitive.
Related Issue(s)
Fixes #19210