minimist: Ambiguous behavior

Please open -a=b=c as a new issue so it can be tracked separately.

(For interest, I fixed a similar bug in early iteration of parseArgs! https://github.com/pkgjs/parseargs/pull/43)

A parser has to decide how to process --foo bar. The default approach in minimist is that options are assumed to take an option-argument if one is available, so this is by default parsed like --foo=bar.

The boolean configuration option changes this default behaviour. A boolean option is assumed not to take an option argument, so --foo bar is parsed like bar --foo.

An argument with an explicit = like --foo=bar is parsed as an option and its value, whatever the configuration.

I’m comfortable with the current behaviour as being reasonable, but it will be a while before I can double-check my understanding and put a story together.

With the input configuration specifying both opts.boolean:true and opts.string the result is almost by definition ambiguous, so that does fit under the issue title of “Ambiguous behaviour”, whether or not it is intended. 😄

-a-b-c

I think this is by design.

-абв

This falls under the non-alphanumeric handling of the first case, and probably as intended.

-=1

Not sure this is intentional, but the first character after the - is assumed to be an option. Likewise for -+.

In this case the parsing of -1 as an option is intended behaviour. Utilities can use a digit as a short option. For example:

ls -1

This is tested here: https://github.com/minimistjs/minimist/blob/980d7ac61a0b4bd552711251ac107d506b23e41f/test/short.js#L8

Thank you very much for the assist!