Fix: Add cleanup function to useEffect in 03-client-step7 #65
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.
Description
This PR addresses an issue in the
useCounterContract
hook where theuseEffect
hook's recursive function could continue running even after thecounterContract
value changes. This could potentially lead to memory leaks and unnecessary API calls.Changes
useEffect
hook to set a cancellation flag (isCancelled
) when thecounterContract
value changes or the component unmounts.getValue
function now checks theisCancelled
flag to determine whether to continue execution.Testing
counterContract
changes.Related Issues
useCounterContract
.