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
I assume when you say support for "numbers" you are thinking of it as as explicit type specified by the author, rather than auto-detection? (Both minimist and yargs have reported issues about automatic detection going wrong, some false positives of ids, some due to overflow.)
Negative numbers clash with the ability to use a digit as an option, like ls -1. This means some compromises are needed to support negative numbers. There is some prior discussion in a PR that proposed one form of negative number support in pkgjs/parseargs#62
I'm comfortable with parseArgs staying simple and not supporting type conversions. (But I am also very comfortable reaching for a library when I need more!)
What is the problem this feature will solve?
In today's @nodejs/tooling WG meeting, we're discussing the parseArgs that the config supports only either boolean or string for parsing args.
nodejs/tooling#155
What is the feature you are proposing to solve the problem?
I'd like to open for discussion on whether we should support other primitive types such as numbers and complex types such as Streams.
There're some concerns about it but I think it will be worth it to hear what other people think about it
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: