You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, nargs didn't consume dashed arguments since version 9.0.0. So, issue #232 was opened, and new configuration option, nargs-eats-options, was added (thanks to @bcoe).
By now, after the fix, nargs-eats-option works well with one-value options but still doesn't work with options which are considered as arrays.
For example, --foo is an array option (and nargs is set to 1): --foo -apple --foo banana -foo cat
is not parsed correctly even with nargs-eats-option=true .
Expected result is: foo: [ '-apple', 'banana', 'cat' ].
Actual result is: foo: ['banana', 'cat' ].
And this works correct in version 8.1.0, result is foo: [ '-apple', 'banana', 'cat' ] as expected.
The text was updated successfully, but these errors were encountered:
Firstly, nargs didn't consume dashed arguments since version 9.0.0. So, issue #232 was opened, and new configuration option,
nargs-eats-options
, was added (thanks to @bcoe).By now, after the fix,
nargs-eats-option
works well with one-value options but still doesn't work with options which are considered as arrays.For example, --foo is an array option (and nargs is set to 1):
--foo -apple --foo banana -foo cat
is not parsed correctly even with
nargs-eats-option=true
.Expected result is:
foo: [ '-apple', 'banana', 'cat' ]
.Actual result is:
foo: ['banana', 'cat' ]
.And this works correct in version 8.1.0, result is
foo: [ '-apple', 'banana', 'cat' ]
as expected.The text was updated successfully, but these errors were encountered: