Schematics: add schematic for component store

[brandonroberts]

Add a new schematic to generate:

A service that extends ComponentStore
A spec file if requested
Maybe an inlined interface for the default type

Describe any alternatives/workarounds you're currently using

Other information:

If accepted, I would be willing to submit a PR for this feature

[ ] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No

[ilyaryabchinski]

Wanted to grab this, but didn't find the way how to run schematics locally(not from node_modules) 😢

[santoshyadavdev]

Hey @ilyaryabchinski if you want to start I can help.

[ilyaryabchinski]

Hey @santoshyadavdev! would be nice

So I am trying to run schematics directly from the repo, but get an error. What am I doing wrong?

[santoshyadavdev]

It's easy to write test for schematics and verify rather than trying to run it locally. You can see any existing test case. You can share the repo with me to check as well.

[timdeschryver]

As @santoshyadavdev pointed out, the easiest way to test a schematic is via unit tests.
What I do if I want to test them out in a project is to build to project and use npx to to run the schematic.
The angular docs have a section that can help you with it (via npm link).
I hope this helps you a bit, if not feel free to ping us 🙂

[rovshenn]

I am planning to look into this as there seem to be no open PR :) I have had some schematics experience

[rovshenn]

@brandonroberts @timdeschryver and @alex-okrushko
I am wondering what the template for the auto generated component store service should contain.
Where do you want to discuss it guys?

[rovshenn]

I am wondering if the component store should be provided for a specific component or a modal or shall we give both selections and let the user narrow down?

I will base my work based off of schematics for effects, as both effects and component store are services

[rovshenn]

@timdeschryver @brandonroberts @alex-okrushko :) any thoughts on above?

[brandonroberts]

Yes I think providing a path to a component should be an option.

[va-stefanek]

@brandonroberts Would you prefer to support two ways of providing a store: module's path and component's path or just one of them (component)? In case of component should we also always inject component store to the constructor? Do we allow to not specify neither of them and generate component store with providedIn: 'root' then?