-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Allow boolean default for flag option #987
Merged
shadowspawn
merged 5 commits into
tj:release/3.0.0
from
shadowspawn:feature/928-allow-boolean-default
Jul 25, 2019
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5a27ec4
Add support for default value for boolean flags
shadowspawn 3ff940b
Expand testing for boolean flags to cover new features
shadowspawn b3ccac2
Add written description of boolean default value for --foo/--no-foo
shadowspawn e346d67
Avoid eslint warnings for requiring shouldjs in simple way
shadowspawn bb4af52
Restore test.options.bool.small.js, KISS
shadowspawn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,28 @@ | ||
/** | ||
* Module dependencies. | ||
*/ | ||
const commander = require('../'); | ||
// eslint-disable-next-line no-unused-vars | ||
const should = require('should'); | ||
shadowspawn marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
var program = require('../') | ||
, should = require('should'); | ||
// Test simple flag and negatable flag | ||
|
||
program | ||
.version('0.0.1') | ||
.option('-p, --pepper', 'add pepper') | ||
.option('-c, --no-cheese', 'remove cheese'); | ||
function simpleFlagProgram() { | ||
const program = new commander.Command(); | ||
program | ||
.option('-p, --pepper', 'add pepper') | ||
.option('-C, --no-cheese', 'remove cheese'); | ||
return program; | ||
} | ||
|
||
program.parse(['node', 'test', '--pepper']); | ||
program.pepper.should.be.true(); | ||
program.cheese.should.be.true(); | ||
const simpleFlagNoOptions = simpleFlagProgram(); | ||
simpleFlagNoOptions.parse(['node', 'test']); | ||
simpleFlagNoOptions.should.not.have.property('pepper'); | ||
simpleFlagNoOptions.cheese.should.be.true(); | ||
|
||
const simpleFlagLong = simpleFlagProgram(); | ||
simpleFlagLong.parse(['node', 'test', '--pepper', '--no-cheese']); | ||
simpleFlagLong.pepper.should.be.true(); | ||
simpleFlagLong.cheese.should.be.false(); | ||
|
||
const simpleFlagShort = simpleFlagProgram(); | ||
shadowspawn marked this conversation as resolved.
Show resolved
Hide resolved
|
||
simpleFlagShort.parse(['node', 'test', '-p', '-C']); | ||
simpleFlagShort.pepper.should.be.true(); | ||
simpleFlagShort.cheese.should.be.false(); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,64 @@ | ||
/** | ||
* Module dependencies. | ||
*/ | ||
|
||
var program = require('../') | ||
, should = require('should'); | ||
|
||
program | ||
.version('0.0.1') | ||
.option('-e, --everything', 'add all of the toppings') | ||
.option('-p, --pepper', 'add pepper') | ||
.option('-P, --no-pepper', 'remove pepper') | ||
.option('-c|--no-cheese', 'remove cheese'); | ||
|
||
program.parse(['node', 'test']); | ||
program.should.not.have.property('everything'); | ||
program.should.not.have.property('pepper'); | ||
program.cheese.should.be.true(); | ||
|
||
program.parse(['node', 'test', '--everything']); | ||
program.everything.should.be.true(); | ||
program.should.not.have.property('pepper'); | ||
program.cheese.should.be.true(); | ||
|
||
program.parse(['node', 'test', '--pepper']); | ||
program.pepper.should.be.true(); | ||
program.cheese.should.be.true(); | ||
|
||
program.parse(['node', 'test', '--everything', '--no-pepper', '--no-cheese']); | ||
program.pepper.should.be.false(); | ||
program.cheese.should.be.false(); | ||
const commander = require('../'); | ||
// eslint-disable-next-line no-unused-vars | ||
const should = require('should'); | ||
|
||
// Test combination of flag and --no-flag | ||
// (negatable flag on its own is tested in test.options.bool.js) | ||
|
||
function flagProgram(defaultValue) { | ||
const program = new commander.Command(); | ||
program | ||
.option('-p, --pepper', 'add pepper', defaultValue) | ||
.option('-P, --no-pepper', 'remove pepper'); | ||
return program; | ||
} | ||
|
||
// Flag with no default, normal usage. | ||
|
||
const programNoDefaultNoOptions = flagProgram(); | ||
programNoDefaultNoOptions.parse(['node', 'test']); | ||
programNoDefaultNoOptions.should.not.have.property('pepper'); | ||
|
||
const programNoDefaultWithFlag = flagProgram(); | ||
programNoDefaultWithFlag.parse(['node', 'test', '--pepper']); | ||
programNoDefaultWithFlag.pepper.should.be.true(); | ||
|
||
const programNoDefaultWithNegFlag = flagProgram(); | ||
programNoDefaultWithNegFlag.parse(['node', 'test', '--no-pepper']); | ||
programNoDefaultWithNegFlag.pepper.should.be.false(); | ||
|
||
// Flag with default, say from an environment variable. | ||
|
||
const programTrueDefaultNoOptions = flagProgram(true); | ||
programTrueDefaultNoOptions.parse(['node', 'test']); | ||
programTrueDefaultNoOptions.pepper.should.be.true(); | ||
|
||
const programTrueDefaultWithFlag = flagProgram(true); | ||
programTrueDefaultWithFlag.parse(['node', 'test', '-p']); | ||
programTrueDefaultWithFlag.pepper.should.be.true(); | ||
|
||
const programTrueDefaultWithNegFlag = flagProgram(true); | ||
programTrueDefaultWithNegFlag.parse(['node', 'test', '-P']); | ||
programTrueDefaultWithNegFlag.pepper.should.be.false(); | ||
|
||
const programFalseDefaultNoOptions = flagProgram(false); | ||
programFalseDefaultNoOptions.parse(['node', 'test']); | ||
programFalseDefaultNoOptions.pepper.should.be.false(); | ||
|
||
const programFalseDefaultWithFlag = flagProgram(false); | ||
programFalseDefaultWithFlag.parse(['node', 'test', '-p']); | ||
programFalseDefaultWithFlag.pepper.should.be.true(); | ||
|
||
const programFalseDefaultWithNegFlag = flagProgram(false); | ||
programFalseDefaultWithNegFlag.parse(['node', 'test', '-P']); | ||
programFalseDefaultWithNegFlag.pepper.should.be.false(); | ||
|
||
// Flag specified both ways, last one wins. | ||
|
||
const programNoYes = flagProgram(); | ||
programNoYes.parse(['node', 'test', '--no-pepper', '--pepper']); | ||
programNoYes.pepper.should.be.true(); | ||
|
||
const programYesNo = flagProgram(); | ||
programYesNo.parse(['node', 'test', '--pepper', '--no-pepper']); | ||
programYesNo.pepper.should.be.false(); |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In rereading this and the edits, I'm not sure we're using consistent vocabulary on this specific line; i.e. it can be unclear whether "define" (or "specify", "add", "set", etc.) means "when defining the program" or "when invoking the program via the CLI."
It could just be that the sentence is slightly awkwardly worded (and sorry to comment on something that isn't a change in this commit).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the awkward and potential for misinterpretation. I have struggled with the wording a couple of times, but at least we do have examples to consult. I'm not planning to have another go in this PR.