Skip to content

fix(paths): allow specifying paths to a component when generating #267

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

Closed
wants to merge 1 commit into from

Conversation

Brocco
Copy link
Contributor

@Brocco Brocco commented Mar 1, 2016

When generating a component allow to specify the path the where the component will go
ng generate component foo/bar/person will create the component (and all associated files)
in the directory [project-root]/src/app/foo/bar/person/

When generating a component allow to specify the path the where the component will go
`ng generate component foo/bar/person` will create the component (and all associated files)
in the directory `[project-root]/src/app/foo/bar/person/`
@Brocco
Copy link
Contributor Author

Brocco commented Mar 1, 2016

This is an initial implementation, upgrade to this will be to allow for relative paths based upon user's current working directory

@cironunes
Copy link
Member

👍

@hansl
Copy link
Contributor

hansl commented Mar 1, 2016

Nice! LGTM

@Brocco Brocco closed this in e802a8f Mar 1, 2016
@Brocco Brocco deleted the component-paths branch March 2, 2016 02:08
hansl pushed a commit to hansl/angular-cli that referenced this pull request Mar 4, 2016
When generating a component allow to specify the path the where the component will go
`ng generate component foo/bar/person` will create the component (and all associated files)
in the directory `[project-root]/src/app/foo/bar/person/`
Closes angular#267
@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 Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants