More than one --option

[shannonmoeller]

The current documentation on using grunt.option is misleading. It says that boolean flags and options with values are supported, but what it doesn't tell you is that you can't have both at the same time.

// Gruntfile.js -> grunt --foo
module.exports = function(grunt) {
    assert.strictEqual(grunt.option('foo'), true); // pass
    grunt.registerTask('default', []);
};

// Gruntfile.js -> grunt --bar=42
module.exports = function(grunt) {
    assert.strictEqual(grunt.option('bar'), 42);   // pass
    grunt.registerTask('default', []);
};

// Gruntfile.js -> grunt --foo --bar=42
module.exports = function(grunt) {
    assert.strictEqual(grunt.option('foo'), true); // fail -> foo === '--bar=42'
    assert.strictEqual(grunt.option('bar'), 42);   // fail -> bar === undefined
    grunt.registerTask('default', []);
};

I've written a plugin called nopt-grunt that provides a work around, but it's far from ideal. While it allows you to define and use options as expected, they get added too late in the process to be documented by grunt --help.

Misleading:

• http://gruntjs.com/api/grunt.option
• http://gruntjs.com/frequently-asked-questions#options

TODO:

• http://gruntjs.com/creating-tasks#cli-options-environment

[yuanyan]

If you try grunt --bar=42 --foo, it's will be work right. Is this a bug of the nopt? @isaacs

[shannonmoeller]

That is a workaround, not a fix. For example grunt test --bar=42 --foo --baz --bat will still behave inconsistently. The primary issue is that Gruntfile authors are not given a way to properly configure options. They can always parse the options themselves, but that's frustrating when Grunt already gets you 80% of the way there.

[yuanyan]

I test the latest version of nopt that have fix this problem.

[vladikoff]

This is a known issue, tracking in #908
Thanks!