-
Notifications
You must be signed in to change notification settings - Fork 12k
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.
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
Consistent naming of options and arguments that do the same thing #12784
Comments
I prefer |
Let's review it for v8. We have a design in place and a discussion. |
… that do the same thing This aligns options that do the same thing: 1) `skipSpecs` and `spec` has been deprecated in favor of `skipTests`. 2) `styleext` has been deprecated in favor of `style` since the latest is two words. Fixes #12784
When I create a new project using the just-released 6.2 CLI and The PR clearly states "styleext has been deprecated in favor of style since the latest is two words.", so this appears to be have been overlooked for new project creation. |
@alan-agius4 @hansl @kyliau See above - behavior hasn't changed in the latest version so just checking if anyone saw this comment. |
@EatonZ, just saw your comment. Ideally, you open new issue when there is a bug. That said, I will land a PR for this soon, since it's a minor thing. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
At the moment, certain options and arguments that do the same thing should are not named the same across all schematics.
In
ng new
to skip the creation of spec files, one needs to use--skip-test
, with an alias of-S
, while in other schematics it is--spec
and no alias.In the component schematics
ng generate component
, to specify the style preprocessor you need to use--styleext
, while inng new
this is named--style
We should discuss this, choose the preferred namings and align all the same options to make it easier for the users.
The text was updated successfully, but these errors were encountered: