fix(run): warn on incompatible arguments with useNx #3326
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
fahslaj
force-pushed
the
run-warn-on-incompatible-args
branch
from
1dc2d11
to
5ddf597
Compare
fahslaj
force-pushed
the
run-warn-on-incompatible-args
branch
from
5ddf597
to
79dc068
Compare
JamesHenry
approved these changes
Sep 20, 2022
JamesHenry
changed the title
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Makes
lerna runwarn the user when --sort, --no-sort, --include-dependencies, and --parallel are used with a nx.json file.Description
Motivation and Context
This change is necessary to communicate that specific options are not available when using nx with a custom nx.json file.
How Has This Been Tested?
This has been tested manually and covered by e2e tests.
Types of changes
Checklist: