Skip to content

[parser] combining aliases in ng new don't work #16614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 15 tasks
johnpapa opened this issue Jan 9, 2020 · 1 comment · Fixed by #22778
Closed
1 of 15 tasks

[parser] combining aliases in ng new don't work #16614

johnpapa opened this issue Jan 9, 2020 · 1 comment · Fixed by #22778
Labels
area: @angular/cli freq1: low Only reported by a handful of users who observe it rarely severity5: regression type: bug/fix
Milestone
Backlog

Comments

@johnpapa
Copy link
Contributor

johnpapa commented Jan 9, 2020 •
edited
Loading

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • xi18n
  • run
  • config
  • help
  • version
  • doc

Is this a regression?

Yes, the previous version in which this bug was not present was: ....

Yes - I can't recall when it worked last though

Description

A clear and concise description of the problem...

When combining multiple aliases such as -s and -t, they don't all work. It seems only the first one is applied.

🔬 Minimal Reproduction

ng new app01 --style scss -st --routing -d

🔥 Exception or Error

Notice the output (reduced to show the component only)


...
CREATE app01/src/app/app.module.ts (393 bytes)
CREATE app01/src/app/app.component.scss (0 bytes) 👈
CREATE app01/src/app/app.component.spec.ts (1095 bytes)
CREATE app01/src/app/app.component.ts (1505 bytes)
...

This should have created app.component.ts and the spec, only.

But if I use the command ng new app01 --style scss -s -t --routing -d I do get the desired outcome (because they are separated
@ngbot ngbot bot added this to the needsTriage milestone Jan 9, 2020
@alan-agius4 alan-agius4 added the freq1: low Only reported by a handful of users who observe it rarely label Jan 9, 2020
@ngbot ngbot bot modified the milestones: needsTriage, Backlog Jan 9, 2020
@alan-agius4 alan-agius4 changed the title combining aliases in ng new don't work [parser] combining aliases in ng new don't work Jan 9, 2020
@alan-agius4 alan-agius4 mentioned this issue Feb 28, 2022
Merged
alan-agius4 added a commit that referenced this issue Mar 9, 2022
@alan-agius4
refactor(@angular/cli): replace command line arguments parser
2e04931 
With this change we refactor the Angular CLI and replace the underlying args parser and command builder. We choose to use Yargs as our parser and command builder of choice. The main advantages of Yargs over other command builders are;

- Highly configurable.
- We already use it in other packages such as the compiler-cli/dev-infra etc..
- Commands and options can be added during runtime. This is a requirement that is needed to support architect and schematics commands.
- Outstanding documentation.
- The possibility to parse args without parser configuration (Free form).
- Commands are built lazily based on the arguments passed.

BREAKING CHANGE:

Several changes in the Angular CLI commands and arguments handling.

- `ng help` has been removed in favour of the `—-help` option.
- `ng —-version` has been removed in favour of `ng version` and `ng v`.
- Deprecated camel cased arguments are no longer supported. Ex. using `—-sourceMap` instead of `—-source-map` will result in an error.
- `ng update`, `—-migrate-only` option no longer accepts a string of migration name, instead use `—-migrate-only -—name <migration-name>`.
- `—-help json` help has been removed.

Closes #20976, closes #16614 and closes #16241
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area: @angular/cli freq1: low Only reported by a handful of users who observe it rarely severity5: regression type: bug/fix
Projects
None yet
Milestone
Backlog
Development

Successfully merging a pull request may close this issue.

refactor(@angular/cli): replace command line arguments parser
2 participants
@johnpapa @alan-agius4