[Feature] Do not allow passing w CLI flag without argument
#4577
Labels
Comments
|
Sounds like a great idea! Would you like to contribute this change to Jest? :) |
cpojer
pushed a commit
that referenced
this issue
Oct 3, 2017
…#4591) * Check if the maxWorkers has a value and raises an exception otherwise In this commit we are adding a new validation in the check method of the jest-cli package, so we raise an exception if the user tries to run Jest with undefined maxWorkers, e.g. jest --maxWorkers jest --maxWorkers 2 Some users were confusing -w as an alias to --watch, but in fact it is an alias to --maxWorkers. This change will also make this distinction clearer. Fixes issue #4577 * Add expected exception message in the check method tests * Improve error message for when maxWorkers is undefined
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
jest -wwill happily run, and I have no clue why watch mode isn't working - it's not working because-wis not for watch mode but for specifying number of workers. It should be easy to throw an error when I don't pass in the number of workers (bonus points for hinting at--watchflag).The text was updated successfully, but these errors were encountered: