-
Notifications
You must be signed in to change notification settings - Fork 12k
DOCS (guide): change Generating Components, Directives, Pipes and Services section #5470
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
Conversation
Change in a update version of README to create a new PR (as suggest by Brocco)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small change please, otherwise LGTM.
README.md
Outdated
angular-cli will add reference to `components`, `directives` and `pipes` automatically in the `app.module.ts`. If you need to add this references to another custom module, follow this steps: | ||
|
||
1. `ng g module newModule` to create a new module | ||
2. call `ng g component new-module/newComponent` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you change newComponent
and newModule
to dash-case
instead? That's how we show these overall in the documentation.
@filipesilva done 😃 |
Change in a update version of README to create a new PR (as suggest by Brocco) Close #5470
Change in a update version of README to create a new PR (as suggest by Brocco) Close #5470
Change in a update version of README to create a new PR (as suggest by Brocco) Close #5470
Change in a update version of README to create a new PR (as suggest by Brocco) Close angular#5470
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. |
Change in a update version of README to create a new PR (as suggest by Brocco)