Open in StackBlitz

npm i https://pkg.pr.new/release-it@1215

commit: 12910a3

Thanks Michal

The idea is that you can negate using --no- e.g. --no-git.commit (https://www.npmjs.com/package/yargs-parser#boolean-negation)

It's cool if we'd be able to use =false (and =0?) to negate as well, but it is not documented: https://www.npmjs.com/package/yargs-parser - any chance you could squeeze in a test somewhere?

Actually, both are supported by yargs, where --no flags being an extra feature (can be disabled). When using in scripts, its often more readable to do --foo=$FOO_ENABLED then building FOO_ARG variable. Yargs is sadly lacking documentation in some regards.

About unit test, thats good idea.

Thanks Michal
The idea is that you can negate using --no- e.g. --no-git.commit (https://www.npmjs.com/package/yargs-parser#boolean-negation)
It's cool if we'd be able to use =false (and =0?) to negate as well, but it is not documented: https://www.npmjs.com/package/yargs-parser - any chance you could squeeze in a test somewhere?

Actually, both are supported by yargs, where --no flags being an extra feature (can be disabled). When using in scripts, its often more readable to do --foo=$FOO_ENABLED then building FOO_ARG variable. Yargs is sadly lacking documentation in some regards.

Good point, haven't used it that way yet.

About unit test, thats good idea.

Thanks!

I've refactored bin to args.js, so it is testable. Testing whole bin js is problematic (but can be done).

This is great! Thanks.

🚀 This pull request is included in v19.0.0-next.4. See Release 19.0.0-next.4 for release notes.