feat(schematics): add component store schematics

[stefanoww]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngrx/platform/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Closes #2570

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information

[ngrxbot]

Preview docs changes for 7fc3766 at https://previews.ngrx.io/pr2886-7fc3766a/

[brandonroberts]

You need to run yarn copy:schematics to copy the schematics-core into the other libraries. That should fix the CI error

[va-stefanek]

You need to run yarn copy:schematics to copy the schematics-core into the other libraries. That should fix the CI error

@brandonroberts It cause newly added methods disappearing from the ast-utils.ts. Is that expected?

[brandonroberts]

Yes. You need to add the changes to modules/schematics-core first, then run the command to sync the changes in all the libraries. We do it this way because it's not currently a standalone package

[va-stefanek]

@brandonroberts seems to be fine now despite of Labeler which probably fail for the forks.

[brandonroberts]

One request would be to change the test scaffolding to not use the TestBed, and just create a new instance of the ComponentStore

cc: @alex-okrushko

[stefanoww]

@brandonroberts done.

[fgoulet]

While waiting for the PR to be reviewed, is there a sample of a spec file generated with this schematic somewhere ? I'm looking for something to help me with unit testing in component store.

[brandonroberts]

The spec is pretty minimal. The <% references are just placeholders

import { <%= classify(name) %>Store } from './<%= dasherize(name) %>.store';

describe('<%= classify(name) %>Store', () => {
  const componentStore = new <%= classify(name) %>Store();

  it('should be created', () => {
    expect(componentStore).toBeTruthy();
  });
});