Skip to content
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

Support relative pathing for ng generate statements #6684

Open
stweedie opened this issue Jun 14, 2017 · 2 comments
Open

Support relative pathing for ng generate statements #6684

stweedie opened this issue Jun 14, 2017 · 2 comments
Labels
area: schematics/angular feature: insufficient votes Label to add when the not a sufficient number of votes or comments from unique authors feature Issue that requests a new feature
Milestone

Comments

@stweedie
Copy link

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

node: 6.10.2
os: linux x64
@angular/common: 4.1.3
@angular/compiler: 4.1.3
@angular/core: 4.1.3
@angular/forms: 4.1.3
@angular/http: 4.1.3
@angular/platform-browser: 4.1.3
@angular/platform-browser-dynamic: 4.1.3
@angular/router: 4.1.3
@angular/cli: 1.0.4
@angular/compiler-cli: 4.1.3

Repro steps.

From project root:

ng g component ./src/app/components/test

The log given by the failure.

installing component
  create src/app/src/app/components/test/test.component.scss
  create src/app/src/app/components/test/test.component.html
  create src/app/src/app/components/test/test.component.spec.ts
  create src/app/src/app/components/test/test.component.ts

Desired functionality.

Doesn't create src/app under the (already existing) src/app directory.

This is a minor change, but would then allow me to use autocomplete with the generator, even if the immediate fix is to just remove 'src/app' from the file location input before processing.

Mention any other details that might be useful.

@Brocco Brocco self-assigned this Jun 15, 2017
@Brocco Brocco added P5 The team acknowledges the request but does not plan to address it, it remains open for discussion severity2: inconvenient labels Jun 15, 2017
@hansl hansl unassigned Brocco Feb 6, 2018
@filipesilva filipesilva added area: schematics/angular feature Issue that requests a new feature and removed P5 The team acknowledges the request but does not plan to address it, it remains open for discussion severity2: inconvenient labels Oct 1, 2019
@ngbot ngbot bot modified the milestone: Backlog Oct 1, 2019
@angular-robot angular-robot bot added the feature: votes required Feature request which is currently still in the voting phase label Feb 1, 2022
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 1, 2022

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

@ngbot ngbot bot modified the milestones: Backlog, needsTriage Feb 1, 2022
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 21, 2022

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

@angular-robot angular-robot bot added feature: insufficient votes Label to add when the not a sufficient number of votes or comments from unique authors and removed feature: votes required Feature request which is currently still in the voting phase labels Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: schematics/angular feature: insufficient votes Label to add when the not a sufficient number of votes or comments from unique authors feature Issue that requests a new feature
Projects
None yet
Development

No branches or pull requests

5 participants