feat(store): Use createFeature in feature-Schematics

[faragos]

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?

See issue: Closes #3741

[ ] 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 #3741

What is the new behavior?

It uses the new createFeature-API instead of the old createReducer only

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

I'm not sure if it really is a feature. It can also be a refactoring, but it changes the API somewhat so.

[netlify]

✅ Deploy Preview for ngrx-io canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	cf4bf9b
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/63fc8710aa126d000895efed

[timdeschryver]

Thanks for the PR!
I encountered a little issue, see the comments for more info.

[timdeschryver]

Can you also update the PR description and link the correct issue #3741 (instead of 3736).

I'm also thinking of exporting the "old" FeatureKey constant.
This because some schematics like selectors and store are using the FeatureKey constant.

To be safe, we can export the feature, name, reducer, and FeatureKey.

[faragos]

Can you also update the PR description and link the correct issue #3741 (instead of 3736).

I'm also thinking of exporting the "old" FeatureKey constant. This because some schematics like selectors and store are using the FeatureKey constant.

To be safe, we can export the feature, name, reducer, and FeatureKey.

I implemented your suggestions. I'm not quite sure about exporting the old featureKey, because it's redundant. But I understand regarding compatibility it's the easiest solution without changing the import in the module

[timdeschryver]

Thanks @faragos 👏👏

[faragos]

@markostanimirovic I implemented your suggestions. It looks way cleaner now thanks. I also removed the not needed Action import is that fine?

[timdeschryver]

Thank you @markostanimirovic for catching these 😀

[markostanimirovic]

LGTM 👍 Thanks @faragos!