This repository has been archived by the owner on Jul 8, 2021. It is now read-only.
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.
Hello, while writing reducers each action within one store takes the state of the same type as an input. It could be easily omitted by moving the state to the base class.
It would transform this:
into that:
The change that I made is very simple and doesn't conflict with the existing solution. The only downside is that it does not work for effects placed in the store because of their asynchronous nature.
What do you think about my approach? I feel like it would help to reduce what is left off so much hated boilerplate.