fix: Prevents Extra Screen Render when navigation index has not changed #35
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.
What does this PR do?
How should this be manually tested?
Background Information
@gorhom/bottom-sheet
and I was able to trace the issue back to the react-navigation-bottom-sheet repository and fix it here in this PR.❌ Before Video
BEFORE — Renders twice. The second render happens ~1 second after mount. The second render causes the entire screen to be re-rendered, which inadvertently/unexpectedly dismisses the keyboard and clears the text input(s).
Kapture.2025-05-06.at.11.30.09.mp4
✅ After Video
AFTER — Only renders when needed!
Kapture.2025-05-06.at.11.30.45.mp4