fix(misc): allow run-commands to accept readyWhen for a single command #6496
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
@nrwl/workspace:run-commands
does not allow to usereadyWhen
with a single command. This was something that was kind of working before #6448, because we were able to bypass the restriction by usingcommands
with a single command, but if you tried to use it withcommand
it would error. This was inconsistent behavior and not in line with the docs. In #6448 the restriction was "corrected" to match the docs, but there's actually no reason to enforce that and limit that option to only multiple commands.Expected Behavior
@nrwl/workspace:run-commands
should allow usingreadyWhen
with a single command. When running multiple commands,readyWhen
can only be set if theparallel
option is set totrue
.Related Issue(s)
Fixes #