feat(core): add ability to scope plugins #22379
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 3b7cce7. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
FrozenPandaz
force-pushed
the
include-exclude-plugin
branch
3 times, most recently
from
241b727 to
3d5b027
Compare
FrozenPandaz
force-pushed
the
include-exclude-plugin
branch
from
3d5b027 to
3b7cce7
Compare
|
Could this be used to exclude a target for a workspace-level |
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
There is no way to users to filter where plugins are applied. Only by the plugin author.
This means that errors thrown make the plugin unusable and more modifications to the project graph are made than desired.
Expected Behavior
Plugins can be scoped via
includeandexcludewhich are both lists of file patterns.{ plugins: [ { plugin: '@nx/jest/plugin', include: ['packages/**/*'], exclude: ['e2e/**/*'] } ] }This will scope running the plugin to processing only those config files.
Related Issue(s)
Fixes #