parser
parser copied to clipboard
oclif
arg and flag parser for oclif
Consider an arg definition like this: ``` { name: 'something', required: true, parse: input => input.toUpperCase(), options: ['A', 'B'], } ``` Logically an input token of `a` should be acceptable...
It seems that although the presence of a bool flag causes the parsed value to be `true`, the absence of a bool flag causes the parsed value to be `undefined`...
After some investigation, I found that most of all flags created using `flag` object has type `option`. Can you please put the correct type for each of the flag types....
This is mostly a Typescript question more than anything else with OClif itself. I want to create a BaseCommand and define some additional parameters. One such is a getter for...
When `--` is present the rest is taken as arguments. I believe it should be possible to specify the behavior where these "rest" arguments should be distinguishable from other args...
I have a Json file with a properly value pairs. Can I import flags for my CLI from the JSON file or do they necessarily need to be hardcoded?
(Please direct this question to a different repo if warranted). Current implementation: https://github.com/TracerBench/tracerbench/blob/c9b4a5457cfcd21af93dc96f7cd1221eedf6b269/packages/cli/src/helpers/flags.ts#L7-L13 Use-case: We have certain instances where we want to type check and parse flag values differently depending...
Just testing out some Yarn2 support, bumped to the latest version but still getting the same error that's fixed in #71 and on `master`, just not been pushed to NPM....
I thought that by declaring the default attribute in a flag, it would set it to the type I put. But it's `` and it's a problem for me. Is...
Hi, When using `const { args } = this.parse(Command)`, the type of `args` is `any`. This makes it harder to maintain stability when passing those args around. Is it possible...
