Inconsistent naming about argparse HOT 6 CLOSED

It's too late to change API imho. Package is stable. I could consider some change, but only if someone decide to resync this port with latest argparse - that will be a reason to release 2.0.

About 'int' and so on... This is port, it should be as similar as possible. Also, some python types have no equivalent in js. Number is float in js, while int is integer in python.

from argparse.

You are right, these changes can only be considered in release 2.0.

This is port, it should be as similar as possible.
Also, some python types have no equivalent in js. Number is float in js, while int is integer in python.

That's why I prefer the last example )

from argparse.

Imho the best we can do now is to add note to differences list https://github.com/nodeca/argparse#argparse.

I'll keep this open, but honestly, no plans to resync port.

from argparse.

Probably we could support both camelCase & snake_case.

from argparse.

👍

from argparse.

Fixed as part of argparse 2.0.

Use it now like this:

{
     const: ['int' | 'str' | Number | String | ...]
     action: ['store_const' | 'append_const' | ...]
}

Note that while int and str are functions in python, we support them as strings 'int' and 'str' for convenience.

from argparse.