GeezerVison is showing github.com — ng generate component in library doesn't update public_api and exports · Issue #13434 · angular/angular-cli
ng generate component in library doesn't update public_api and exports #13434
Description
Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x ] feature request
Command (mark with an x)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [x ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
Versions:
Angular CLI: 7.2.1
Node: 8.11.3
OS: win32 x64
Angular: 7.2.0
After generating library, I need to add a component to my library by following:
ng generate component foo --project=foo-lib
It doesn't update public_api.ts and exports in my-lib.module.ts file. These steps must be done by hand.
Reacted by Zsofia von Halling, Raúl Julián López Caña, Dalton Willard, Sergey, rveerd, Angel M. Montilla Jiménez, Mazedul Islam, Patrick Ruhkopf, Gianmarco Ferrante, Ties and 2 more
Activity
alan-agius4 commented on Jan 17, 2022
NB: this also applies for modules.
#22511
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