You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Forward unknown command line arguments to jest.config.js file. Right now, jest will respond with "unknown argument'. The proposal is to instead allow these unrecognized arguments so they can be used in the jest.config.js file to modify the config.
Sometimes you want to slightly change the jest config based on some variable. For example, I might want to only run my unit tests or integration tests instead of all my tests. Or I might want to only test a certain project in a monorepo.
Your cli command would look like this: jest --integration
Disabling unknown CLI commands was a conscious decision, to align Jest with a lot of UNIX tools, and we're not going back. We believe this makes sense.
As you already mentioned, this is possible using env variables and I don't see it being more verbose than a CLI flag. I can't see any added value by this proposal, but even more config options to maintain.
Sorry to be a bearer of bad news, but I'm going to close this.
Thanks for taking the time to prepare a nice feature request, appreciated! Looking forward to more proposals or bug fixes :)
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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.