GeezerVison is showing github.com — Support relative pathing for `ng generate` statements · Issue #6684 · angular/angular-cli
Support relative pathing for ng generate statements #6684
Description
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.
Reacted by Kai Röder, Will, Leo Caseiro, Michael Lajlev and Konstantin Shutkin
Activity
angular-robot commented on 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.
angular-robot commented on 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.
Metadata
Metadata
Development
No branches or pull requestsIssue actions