Not sure if this is intended but it seems like the collection.json is missing from tools/schematics, therefore I'm unable to pass aliases to my schematics.
I found the workspace-schematics.json in the final build which is one lined and even if I add the alias there, it will be overwrite after building a new schematic.
I've also tried to create either a collection.json and workspace-schematics.json in tools/schematics but in the former case it will be ignored and in the latter my json is being overwritten.
So basically, I want to be able to edit a somewhat collection.json in order to add aliases, description etc.
At the time, it was generated to make it easier for developers to add new schematics.
I think we could easily update a collection.json when we generate workspace-schematics.
Would people prefer this way?
I would love to be able to configure a collection.json file too: :100: !
Definitely! I think developpers would have more flexibility and power over their schematics. Modifying factory and aliases are a must have I believe. :)
Maybe the workspace-schematic.json should be available for developpers directly in tools/schematics (not the one after building but the one where we develop) which we can configure and that will be one lined after building.
At the time, it was generated to make it easier for developers to add new schematics.
I think we could easily update a
collection.jsonwhen we generateworkspace-schematics.Would people prefer this way?
This would be a great feature :+1:
collection.json is a must and pre-requirement to be able to write tests for custom workspace schematic :)
// no collection no fun! 馃槅
const testRunner = new SchematicTestRunner('schematics', collectionPath);

Hi, sorry about this.
This was mislabeled as stale. We are testing ways to mark _not reproducible_ issues as stale so that we can focus on actionable items but our initial experiment was too broad and unintentionally labeled this issue as stale.
Most helpful comment
At the time, it was generated to make it easier for developers to add new schematics.
I think we could easily update a
collection.jsonwhen we generateworkspace-schematics.Would people prefer this way?