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.
Now that we have React Hooks I've found the
ducks pattern
even more useful! With the[useReducer](https://reactjs.org/docs/hooks-reference.html#usereducer)
hook I can easily switch a duck between using it with redux or auseReducer
.Now the
useReducer
hook require two pieces of data, thereducer
and thedefaultState
. So in my own ducks I've had to also export mydefaultState
to be able to use it with a hook.That way the usage with hooks becomes as follow:
This allows me to choose if I want to use the state locally for the component using
useReducer
or keep it globally in Redux. It also allows me to ex. start out with state in Redux for easy debugging and time traveling and then later take make the state component local if I see that I don't need it globally.I hope you will accept this into the docs, as a consultant (doing both client work and developer training) I love being able to refer colleagues back to this repo as the "canonical" definition of the
Ducks pattern
.