fix: ensure latest values are used when preventRemove
is triggered in usePreventRemove
hook
#11523
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.
Motivation
In
react-navigation/native@6.1.7
with@react-navigation/core@6.4.9
UNSTABLE_usePreventRemove
, whenbeforeRemove
listener is triggered it, it uses old value ofpreventRemove
parameter that's passed into the hook. By using a reference topreventRemove
(andcallback
) we can ensure the latest value is always used.Test plan
Describe the steps to test this change so that a reviewer can verify it. Provide screenshots or videos if the change affects UI.
The change must pass lint, typescript and tests.