-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify that not all configuration options can be overridden by CLI flags #1989
Comments
@novemberborn isn't it better to allow overriding by cli? |
There's some features that should just be configured once and for all, not constantly tweaked through CLI flags. |
This hasn't been a problem for me, but still seems like a strange limitation. Wouldn't it simplify the code to not special-case the configuration? What's actually gained from doing this? If the goal is just to encourage people to use best practices, a more prominent suggestion to use package.json in the docs might be a simpler approach. Or a console warning, rather than actually preventing config on the command line. |
@novemberborn I have updated the docs to clarify the usage of CLI options along with options in package.json. Please take a look into this PR #1993 |
With say the |
Prompted by @Christilut, it's not entirely clear that not all configurations can be overridden by CLI flags. This line should be updated:
See https://github.com/avajs/ava/blob/master/docs/06-configuration.md.
The text was updated successfully, but these errors were encountered: