parseArgs Type Definition

[marcobarrios-fi]

Instead of having a type property with either a "string" or "boolean" value, I believe it would be more intuitive to have a boolean property with either true or false value, with the default value being false.

options: {
  verbose: {
    short: "v",
    boolean: true
  }
}

Furthermore, I would prefer the options to be an array of objects, as this would make it easier work with them.

options: [
  {
    long: "output",
    short: "o",
    required: true
  },
  {
    long: "verbose",
    short: "v",
    boolean: true
  }
}

Thank you for including the parseArgs feature in Node!

[benjamingr]

cc @bcoe @RaisinTen @aduh95 (pinging Ben who added it and some people who reviewed that since I'm not sure what team to ping)

[shadowspawn]

Instead of having a type property with either a "string" or "boolean" value, I believe it would be more intuitive to have a boolean property with either true or false value, with the default value being false.

This was deliberate in case there was expansion of types in the future or by third parties. The original design had a withValue array and the current naming was first discussed in refactor: pkgjs/parseargs#63 (comment)

[shadowspawn]

Furthermore, I would prefer the options to be an array of objects, as this would make it easier work with them.

I think implicitly we were thinking of a key/value lookup of the options properties, but an array could work too. I think the difference is probably not compelling enough to change, also with parseArgs moving to stable in #46640

Proposal for refactor leading to current configuration:
pkgjs/parseargs#45

Edit: Also I don't know if it would be possible to do the strong typing of the parse results in TypeScript if the options configuration was a plain array.

[shadowspawn]

(Two good questions @marcobarriosfi )

[benjamingr]

(The TS bit is possible to type though I actually personally like the current API better)