feature(store): catch action creators being passed to dispatch without () even sooner #2306
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
During the recent merge of NgRx to Google I discovered a number of dispatch calls of new action creators without actual calls, e.g.
store.dispatch(fooAction)
instead ofstore.dispatch(fooAction())
.In NgRx we already added the runtime check, but I think we can do even better and catch it at compile time (IDEs will catch this too).
What is the current behavior?
Errors (warnings) at runtime
What is the new behavior?
Type Error: Functions are not allowed to be dispatched. Did you forget to call action creator?
Does this PR introduce a breaking change?
Other information