You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix the app schematic to use component to create the default component, and module to create the initial module.
Publish a default Angular Collection that contains most blueprints we have and maybe some others
Add options to select a collection and schematic by name.
Add configuration flag in angular-cli.json to use a collection by default, so that ng g my-awesome-schematics will use the default collection which includes my-awesome-schematics.
Being very eager to try this out, I got the new master branch now that the branch is merged and all the critical stuff seems to be there. I created a custom collection (I just took @schematics/angular and changed a few things) and ran ng new -c ./my-own-collection testproject. Which ofc did not work (I see that there are still a few checkmarks not finished ;-) ).
Now, I may be way too early trying this out, but I also did not see any plans for further documentation on this Tracking Issue for the collections. So as a bit of - maybe way to early - feedback, I guess a little bit more documentation how such a collection needs to be set up (or where) in order for something like ng new -c my-own-collection testproject to work, would not hurt. My instinct of just taking your @schematics/angular-collection, modifying it and pointing to the modified version seems to have been the wrong instinct :-D
Could you please provide a documentation? I updated to 1.4.0-rc0 and cant create a component anymore: ng g c not working. ng g component working. ng g component shared/mycomponent (to create component inside module) not working.
Also i dont know what schematics are and the github project doesn't contain any readme.
Reacted by Christian, Danny Mayer, William Grasel, Rafa SA, Bennie Copeland, Jared Szechy and Glenn Vlekke
Activity
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
feat(@angular/cli): Update generate & new to use schematics
Vaelor commentedon Aug 17, 2017
Being very eager to try this out, I got the new master branch now that the branch is merged and all the critical stuff seems to be there. I created a custom collection (I just took
@schematics/angularand changed a few things) and ranng new -c ./my-own-collection testproject. Which ofc did not work (I see that there are still a few checkmarks not finished ;-) ).Now, I may be way too early trying this out, but I also did not see any plans for further documentation on this Tracking Issue for the collections. So as a bit of - maybe way to early - feedback, I guess a little bit more documentation how such a collection needs to be set up (or where) in order for something like
ng new -c my-own-collection testprojectto work, would not hurt. My instinct of just taking your@schematics/angular-collection, modifying it and pointing to the modified version seems to have been the wrong instinct :-DOh and awesome work on this! Thanks a lot!
MickL commentedon Aug 24, 2017
Could you please provide a documentation? I updated to 1.4.0-rc0 and cant create a component anymore:
ng g cnot working.ng g componentworking.ng g component shared/mycomponent(to create component inside module) not working.Also i dont know what schematics are and the github project doesn't contain any readme.
Oddnoun commentedon Oct 6, 2017
Any further updates on this?
Robinyo commentedon Jan 3, 2018
Some Schematics related posts:
feat(@angular/cli): Update generate & new to use schematics
angular-automatic-lock-bot commentedon Sep 7, 2019
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.