Skip to content

provide blueprint for component library as a feature #1284

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.

Sign up for GitHub

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

Jump to bottom
Closed
yeiniel opened this issue Jul 5, 2016 · 8 comments
Closed

provide blueprint for component library as a feature #1284

yeiniel opened this issue Jul 5, 2016 · 8 comments
Labels
feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@yeiniel
Copy link

yeiniel commented Jul 5, 2016

Using angular-cli improve development but something i was missing is a blueprint to create component libraries. Right now i have developed a library of services to be consumed by more than one application and i have to resort to use a yeoman generator. The generator was fine (except for the lack of testing infrastructure) but i prefer a consistent coding style and the best practices that can bring to the table the angular-cli. Any idea if this feature will be included in the roadmap? May be implementing the App Creation Using Template story is the way to achieve this.
@filipesilva filipesilva added feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jul 28, 2016
@filipesilva
Copy link
Contributor

This feature is on roadmap but I have no set date for it.

@kartzum
Copy link

kartzum commented Aug 9, 2016

Ok, but may be have you any advice how to create components/services libraries for angular2 or some manual steps for creating these ones through angular cli?

I tried to create simple library through angular cli (https://github.com/kartzum/color-generators) but got some problems. There are some:

  • 'app' name can not be changed
  • after 'npm publish' package does not contain 'dist' folder without manual steps

@berwyn
Copy link

berwyn commented Aug 9, 2016

I'd like to throw in support for this issue. I have feature teams working vertical slices of the app and it would be great if I could pull those out into separate projects and still use the cli tool!

@filipesilva
Copy link
Contributor

Marking as dupe of #1284 to keep discussion in a single place.

@kartzum
Copy link

kartzum commented Sep 22, 2016

Could you please write link to new discussion?

@yeiniel
Copy link
Author

yeiniel commented Sep 22, 2016

Hey @filipesilva i think you make a mistake marking this as a dupe of #1284 because this is the issue #1284. Is the issue number wrong?

@filipesilva
Copy link
Contributor

@kartzum @yeiniel sorry, my bad! The right link is #1692

@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yeiniel @kartzum @berwyn @filipesilva