9 Commits

Author SHA1 Message Date
Hans Larsen
5faf0cb535 fix(@angular/cli): numerical flags should not give 0 if empty
And numerical positional flags will be ignored.

If the value is an empty string, a number conversion would give 0. It is unexpected
from the user standpoint ("--num=" has the user expect a string value).
2018-09-27 12:46:15 -04:00
Hans Larsen
4daa299558 fix(@angular/cli): allow -a=value arguments
If a flag is followed by an equal sign, just treat it as a long name. So
the example above would translate to --a=value, while -abc=123 would be
"-a -b -c=123".

Fixes #12308
2018-09-27 12:46:15 -04:00
Hans Larsen
78a6fabb4a fix(@angular/cli): allow empty string arguments 2018-09-27 12:46:15 -04:00
Hans
97576ecd13 fix(@angular/cli): do not show stack on argument parse error 2018-09-19 13:02:40 -07:00
Hans
f7f5b28dae feat(@angular/cli): if parsing comes accross an obvious error throw it
We accumulate errors this way, and throw only once at the end, with messages for
all errors.
2018-09-19 13:02:40 -07:00
Hans
7d782a3f5e feat(@angular/cli): add support for parsing enums
Options can now contain enumerations of values.
2018-09-19 13:02:40 -07:00
Hans
34818b0346 feat(@angular/cli): add subcommand to options
SubCommands are not tied to the option that triggers them. They
contain a subset of a CommandDescription interface, with at least
a short and long description and usage notes. These are generated
from the subcommand schema (e.g. schematics in case of generate).
2018-09-19 13:02:40 -07:00
Hans
66fbc59767 feat(@angular/cli): add long description and suboption option type 2018-09-06 07:37:48 -07:00
Hans
ff1baab7fc feat(@angular/cli): remove yargs-parser and implement parsing
This is fully backward compatible.
2018-09-06 07:37:48 -07:00