According to the docs we should generate three files.
todos.store.ts
todos.store.spec.ts
todos.events.ts
This could also look for the closest module and automatically add the store as a declaration and use it in the forRoot or forFeature functions.
leon
All 8 comments
If someone wants ot take this on, here is a example of some schematics I wrote for Material - https://github.com/angular/material2/tree/master/schematics
amcdnl
on 5 Mar 2018
I can take this one /Mike
BeastCode
on 5 Mar 2018
Hi,
I created schematics for ngxs:store, action & selector. I still needs some work, but I'll submit a PR for what I have so far, to open it up for comments and enhancements.
Should I create a new folder for schematics under tools or somewhere else?
Do we still want actions to use the name .events.ts, I see multiple examples that use .action.ts?
/Mike
BeastCode
on 9 Apr 2018
Closing and marking for future.
amcdnl
on 8 May 2018
@BeastCode Did you get anywhere with creating this PR?
markwhitfeld
on 21 Aug 2018
Hello, I would like to take this issue. Is there any work in progress or should I start from scratch?
@amcdnl posted a link to material's schematics, but it has been moved:
https://github.com/angular/material2/tree/master/src/lib/schematics
boulix3
on 21 Aug 2018
This would be a great addition :)
mackelito
on 28 Aug 2018
splincode
on 26 Nov 2018
Related issues
malfusion
路
4Comments
abalad
路
5Comments
Newbie012
路
4Comments
paulstelzer
路
5Comments
ToxicToast
路
6Comments
Most helpful comment
Hi,
I created schematics for ngxs:store, action & selector. I still needs some work, but I'll submit a PR for what I have so far, to open it up for comments and enhancements.
Should I create a new folder for schematics under tools or somewhere else?
Do we still want actions to use the name .events.ts, I see multiple examples that use .action.ts?
/Mike