Arguments parsed to numbers incorrectly. about nopt HOT 10 CLOSED

FWIW, jQuery did something like this at one point trying to make their data- attribute parsing smart and it ended up being a bit of a mess.

from nopt.

Just specify it to be a string by providing knownOpts. Your proposed behaviour would not be desirable for me since I often use scientific notation to specify numeric values (e.g. -n 1e6).

from nopt.

@michaelficarra In this case, these are unexpected arguments.

from nopt.

If unexpected were always stored as strings (maybe an option could be added to enable this) then it could be up to the end-user how they wanted to coerce or parse that string value. Which would solve both problems, I think.

from nopt.

Yes, I could agree with that.

from nopt.

This is how I'd do it. Create an option whereby a "reviver" method (like JSON.parse has) can be specified for unknown values, with the default being the current behavior. Then, if I want every unknown value to be a string, the reviver method I'd specify is function(s) { return s; }.

from nopt.

I could see adding a type that preserves trailing/leading zeroes like you describe. It shoudln't be too hard to do in your app with a custom type, but you'll probably have to look at the nopt and/or npm source to see how to go about it. Doc patch welcome.

from nopt.

I'm talking about unexpected arguments.

from nopt.

Oh, right. Sure, patch welcome.

from nopt.

(maybe an option could be added to enable this)

Please, no additional options. Just unconditionally treat unexpected values as strings.

from nopt.