Implement ngrx rules for @angular-devkit/schematics

[robwormald]

Pretty soon here the Angular team will be releasing Schematics, a new library for doing code generation and modification. It's the tool Angular CLI will use for generating components, tests, etc.

It's extensible, so we should develop a set of Rules for schematics that handle some of the boilerplate of ngrx. Things like:

• generating reducers and tests
• generating reducers w/ a set of passed actions
• generating CRUD-reducers
• creating effects
• etc

This is blocked proper until a release of Schematics, but feedback on what kind of rules would be useful is welcome.

[sharikovvladislav]

This news are awesome! Can't wait I can try this and probably help with testing :)

1. Do you have any information about the possible release dates of the library?
2. I think that a rule to create "feature module" might be useful. I mean some command that will create whole feature module with some base structure (reducer, effects file, actions file, core module, core container may be).

[sharikovvladislav]

@robwormald Any plans on this? Schematics was shipped in cli 1.4 if I remember correctly.

[ghost]

I love @ngrx/platform; however, my only concern since the release of these state management packages has been the documentation. To be more specific, I feel the documentation and corresponding samples could be more clear and concise. Presently, it seems lack of clarity in the documentation surfaces as project filesystem structures begin to deviate from the shape of the example-app. I know the documentation is revised continuously. I believe it would of benefit to newcomers if the documentation more closely represented the official angular documentation of the format from angular.io guides. It would be awesome to see @ngrx/platform documentation as it relates to Schematics rules upon release take the initiative to supply the aforementioned documentation format to promote ease of adoption.

[kuncevic]

is there any documantation on codegen and schematics yet?

[MikeRyanDev]

@kuncevic No, we have a lot more work to do before we consider either of those projects released.

[kuncevic]

@MikeRyanDev both saying "version": "4.1.1", in package.json so I thought that is something that ready to go.

[MikeRyanDev]

No, they are not published to NPM. That version number in package.json is a byproduct of the release process for our other packages.

[RoopeHakulinen]

@MikeRyanDev I would be interested in testing once you think it is ready for it and I'd be willing to help with documentation also if necessary.

[ghost]

@MikeRyanDev I am also interested in testing and would be willing to help with documentation.