Enhance useReducer example and add section on explicit typing#800
Merged
Conversation
maurer2
changed the title
useReducer and add section on explicit typinguseReducer example and add section on explicit typing
ShunMaster1405
approved these changes
Mar 7, 2026
ShunMaster1405
approved these changes
Mar 7, 2026
ShunMaster1405
approved these changes
Mar 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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,
I noticed that in the
useReducersection, the introductory text strongly recommends adding a return type for the reducer, but the code example does not include one. Additionally, I added a section on explicit typing foruseReducerfor cases where TypeScript can't infer the correct types from the reducer, as mentioned in the React 19 upgrade guideCheers