feat(filter-options): Allow command to continue if no packages are matched #2280
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.
Description
continueIfNoMatch
infilterPackages()
to prevent an exception from being thrown if all filters did not match any package.--continue-if-no-match
as a Filter option to enable/disable new param.Motivation and Context
My motivation is being able to execute the same command in one or more Lerna-managed mono repos, which may or may not contain the same scopes. As long as every team follows the definition of scopes, the same CI can be applied to every team.
For example:
The CI tries to create a scope like
--scope <team>-<type-of-artifact>-*
. With this new option, we don't need to conditionally select which artifacts to build. For example, building libs of Team B would fail in the current behavior.Imagine also some people may have suggested adding empty packages only to bypass CI.
How Has This Been Tested?
I have added unit tests to cover the new param. They contain the same scenarios by the tests that throw the exception (plus the new param);
Types of changes
Checklist: