We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using ng g @ngrx/schematics:feature +state/app --group -c to generate a feature state with new createAction() results in following code:
ng g @ngrx/schematics:feature +state/app --group -c
createAction()
export Union = typeof all;
Should be:
export type Union = typeof all;
"@ngrx/schematics": "8.0.0-beta.0"
[x] Yes (Assistance is provided if you need help submitting a pull request) [ ] No
The text was updated successfully, but these errors were encountered:
Before picking this up, do we want to use union to export the actions or are we simply going to export the action creators?
union
Sorry, something went wrong.
Good point, the new createReducer() does not need to have the action union type definition.
createReducer()
Maybe it would avoid possible errors to use the union type in the reducer function as well.
See #1746 discussion about the state type.
This adds reducer schematics with createReducer and doesn't include any unions as we don't explicitly need them. #1785
createReducer
This is resolved via #1785.
No branches or pull requests
Minimal reproduction of the bug/regression with instructions:
Using
ng g @ngrx/schematics:feature +state/app --group -c
to generate a feature state with newcreateAction()
results in following code:export Union = typeof all;
Expected behavior:
Should be:
export type Union = typeof all;
Versions of NgRx, Angular, Node, affected browser(s) and operating system(s):
"@ngrx/schematics": "8.0.0-beta.0"
Other information:
I would be willing to submit a PR to fix this issue
[x] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No
The text was updated successfully, but these errors were encountered: