Summary
react-doctor cannot explicitly re-enable lint / deadCode from CLI when those are disabled in config.
Current behavior
If config sets:
{
"lint": false,
"deadCode": false
}
you can disable via --no-lint / --no-dead-code, but cannot re-enable using --lint / --dead-code because those flags do not exist.
Why this is a problem
README says CLI flags override config, but this only works one-way for booleans.
Reproduction
- Create
react-doctor.config.json with lint: false and deadCode: false.
- Run
react-doctor ..
- Try to force-enable checks from CLI.
Observed:
--lint -> unknown option
--dead-code -> unknown option
Expected behavior
--lint and --dead-code should exist and override config values to true.
Summary
react-doctorcannot explicitly re-enablelint/deadCodefrom CLI when those are disabled in config.Current behavior
If config sets:
{ "lint": false, "deadCode": false }you can disable via
--no-lint/--no-dead-code, but cannot re-enable using--lint/--dead-codebecause those flags do not exist.Why this is a problem
README says CLI flags override config, but this only works one-way for booleans.
Reproduction
react-doctor.config.jsonwithlint: falseanddeadCode: false.react-doctor ..Observed:
--lint-> unknown option--dead-code-> unknown optionExpected behavior
--lintand--dead-codeshould exist and override config values totrue.