Unknown option swallows a known one about nopt HOT 4 CLOSED

I agree, that would be better. What about this case?

my-program --unknown1 --unknown2

Should that be:

{ unknown1: true
, unknown2: true
}

or

{ unknown1: "unknown2" }

Though it's a bit trickier, I'm tempted to say that the first makes more sense. Ie, an unknown option will not ever take a - prefixed thing as its argument. (If you want to make sure that it takes an argument, you can define it to do so.)

Thoughts?

from nopt.

Yes, that would make sense to me; that if you need to handle a -- prefixed value, you need to define the option, and otherwise any -- prefix introduces a new option.

from nopt.

I've just been bitten by this issue when using Grunt. Any options that Grunt itself doesn't know about are made available to the various tasks, meaning that there are a lot of unknown options being used in the system. As a result of this issue you can only use one --flag and it must be the last argument of the command.

I think the general solution of assuming that unknown arguments won't be prefixed with -- is a good one.

from nopt.

Currently in nopt, any unknown argument must have a = to be assigned a value, otherwise it will be assumed to be a boolean. This is no longer an issue.

from nopt.