Closed lcabral37 closed 2 years ago
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
When passing some complex parameters to a command, dot notation parameters and parameters containing spaces do not get properly invoked to the final command. For example , assuming the nx
app-e2e:e2e
target command iswdio run wdio.conf.js
the following commandnx run app-e2e:e2e --cucumberOpts.timeout=3000 --tags="not @exclude"
would render the final command aswdio run wdio.conf.js --cucumberOpts=[Object] --tags=not @exclude
Note that the
--cucumberOpts.timeout
is no longer present instead having a--cucumberOpts=[Object]
and also the--tags
now only containsnot
(this would also lead to other potential issues when the string contained special characters (parenthesis or quotes))Therefore the final targeted command would not received the same parameters as given originally. These parameters would in fact also be incorrectly invoked in the nx process forks
Expected Behavior
When passing parameters to run-command targets, theses parameters should remain untouched So I would expect the targeted command to be called with
wdio run wdio.conf.js --cucumberOpts.timeout=3000 --tags="not @exclude"
Steps to Reproduce
The current issue should be easy to expose by creating a simple project
And then triggering that command with some complex parameters and see that the output does not match.
Failure Logs
Environment