Note that tsc fails with certain argument options #757
Conversation
Documenting the conclusion of microsoft/TypeScript#18581
| @@ -85,6 +85,7 @@ Option | Type | Default | |||
|
|
|||
| * <sup>[1]</sup> These options are experimental. | |||
| * <sup>[2]</sup> These options are only allowed in `tsconfig.json`, and not through command-line switches. | |||
| * Due to a limitation in the argument parser, `tsc` will [fail](https://github.com/Microsoft/TypeScript/issues/18581) on the command line if its last argument is one that can take multiple options (like `--types`) but none are passed. As a workaround you can add another argument at the end, e.g. `tsc --types --pretty`. | |||
There was a problem hiding this comment.
i do not think this is how i would describe the behavior.. it is a feature and not a bug really. it is a command line parser, so not sure what your expectations are for passing flags that expect a value but do not want to pass a value for them..
There was a problem hiding this comment.
Here is how I think about this: the compiler itself does not require that any types are passed, which I know because it works to pass an empty array in a tsconfig. There is no way to specify an equivalent command on the command line. That is what I'm trying to describe here.
Put another way, I don't think the --types flag in particular should require a value on the command line. I'd be fine with any of the syntaxes explored in microsoft/TypeScript#18581 for achieving that.
Or I'm happy to change the description here to clarify the behavior.
There was a problem hiding this comment.
Also, @mhegazy, I used your words from the original issue to describe the behavior: "this a limitation in our commandline parser."
Additionally, the fact that passing no value for --types appears to work if there is another parameter after it supports the idea that this is a valid/expected use case that the argument parser handles incorrectly.
|
We don't need to document every single possible minutae about the commandline parser here. It's a guide, not an exhaustive specification. |
Documenting the conclusion of microsoft/TypeScript#18581