user input validation on argv values about command-line-args

[yoiang]

Hey @75lb ! I've spun up on using command-line-args and it's great! I was looking around for a required flag mechanism and noticed the closed issue, is it something that you feel isn't necessary?

[75lb]

hi @yoiang, yes it was decided to keep input validation out of the library.. it's an opinionated area and best left down-stream..

you can check the output of cli.parse() and if your required value is missing, throw an exception.

[75lb]

glad you like the library, don't be shy to make further suggestions - all good..

[yoiang]

Gotcha, thanks :)

[xescugc]

So the only way right now is to check the cli.parse()? I think the required flag is a really good idea because you can see the full description of the ARGV in the same part of the code, at the definition.

[75lb]

@xescugc as i said before, required logic is opinionated and varies per option type.. what is required exactly? A value? Two values? Two values of length 3?

The library had a required flag two years ago when it was born, but it was quickly removed to give the user full control over validation logic (what is and is not valid).

[xescugc]

For me the required flag means that the options with this flag are required to the export to execute, maybe another name is present but the name i don't care 😄 it's just the idea behind it. It's not a type/format validation, it s a presence validation. Does it make sense for you?