use schematicCollections instead of defaultCollection

[timdeschryver]

Information

In Angular 14, the defaultCollection is deprecated in favor of schematicCollections, which supports an array of schematics (instead of a single one).
We should update the NgRx schematics to add the ngrx schematics to the collection, instead of overwriting the defaultCollection option.

See angular/angular-cli#22860 for more info.

The code that does this is located at https://github.com/ngrx/platform/blob/master/modules/schematics/src/ng-add/index.ts.

Describe any alternatives/workarounds you're currently using

If you want to pick this issue up, please add a comment below :)

I would be willing to submit a PR to fix this issue

• Yes
• No

[suke]

May I work on this issue?

[markostanimirovic]

@suke Sure!

[timdeschryver]

@suke This can only be done once we've updated Angular to v14 (because that release includes the schematicCollections option).

[suke]

OK! I will work on it when Angular v14 is released!

[timdeschryver]

@suke We've updated the repo to use Angular 14, feel free to work on this.

[suke]

@timdeschryver I would like to discuss a specification.
Should I remove the properties in schema.json and automatically add ngrx schematics to the schematicCollections?

https://github.com/ngrx/platform/blob/master/modules/schematics/src/ng-add/schema.json#L6

[timdeschryver]

Yes, that's a good idea!
I think we could also log an error if schematicCollections is not defined within the workspace.

[suke]

Yes, that's a good idea! I think we could also log an error if schematicCollections is not defined within the workspace.

If schematicCollections is not defined, I can create them automatically, but would you prefer to log an error?

[timdeschryver]

I think throwing would be better, it probably means that the user didn't upgrade Angular.

[suke]

I understand.
I'll make it a spec to throw exception!