setState change to correct manner. update useStep.tsx #4310
Conversation
This file contains 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
Changed the way setState is used.
steveluscher
approved these changes
May 13, 2024
Comment on lines
6
to
8
| const prevStep = () => { | ||
| if (step > 0) setStep(step - 1); | ||
| if (step > 0) setStep((prevStep) => prevStep - 1); | ||
| }; |
There was a problem hiding this comment.
const prevStep = () => setStep((prevStep) => prevStep > 0 ? prevStep - 1 : prevStep);React will not re-render if the state transition results in the same value before and after.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changed the way setState is used. When the state is dependent upon on the val, function format must be used.