fix: don't wrap content with BottomSheetView when enableDynamicSizing is true#26
Open
jeanregisser wants to merge 1 commit intoAppAndFlow:mainfrom
Conversation
|
Thanks for the PR - I'm having the same issue and wrapping everything in BottomSheetView is definitely not a right approach. Hey @janicduplessis, what do you think? |
|
same issue here, maybe we could add a <BottomSheet
screenOptions={{
sheetWrapper: BottomSheetView
}}
/> |
|
Also, would it make sense to add this? as it seems like this lib assumes the old default of undefined=false enableDynamicSizing = true, // same default as lib |
github-merge-queue bot
pushed a commit
to valora-xyz/wallet
that referenced
this pull request
Jan 31, 2025
…e `@interaxyz` fork (#6468) ### Description Migrate `@th3rdwave/react-navigation-bottom-sheet` to `@interaxyz` fork in order to get rid of the patch. The patch changes are implemented in the fork: AppAndFlow/react-navigation-bottom-sheet@main...interaxyz:react-navigation-bottom-sheet:intera-fork ### TODO Migrate back to the original package once AppAndFlow/react-navigation-bottom-sheet#26 is released. ### Test plan * CI * Manually tested on Android/iOS emulators (WalletConnect request) ### Related issues - Related to RET-1308 ### Backwards compatibility Y ### Network scalability NA
github-merge-queue bot
pushed a commit
to valora-xyz/wallet
that referenced
this pull request
Jan 31, 2025
…e `@interaxyz` fork (#6468) ### Description Migrate `@th3rdwave/react-navigation-bottom-sheet` to `@interaxyz` fork in order to get rid of the patch. The patch changes are implemented in the fork: AppAndFlow/react-navigation-bottom-sheet@main...interaxyz:react-navigation-bottom-sheet:intera-fork ### TODO Migrate back to the original package once AppAndFlow/react-navigation-bottom-sheet#26 is released. ### Test plan * CI * Manually tested on Android/iOS emulators (WalletConnect request) ### Related issues - Related to RET-1308 ### Backwards compatibility Y ### Network scalability NA
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
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.
Hey,
This PR is to get the discussion started on the following problem:
We're using
react-navigation-bottom-sheetwithenableDynamicSizingset totruebut want to useBottomSheetScrollView(or other Gorhom components:BottomSheetFlatList,BottomSheetSectionList, etc)within the screen to get proper sizing and all features that go with it (scroll down to dismiss, etc).
Currently with the latest version of
react-navigation-bottom-sheet(0.3.2), this causes sizing issues and blank renders.I tracked it down to having both
BottomSheetView(in this lib) andBottomSheetScrollView(in our own screen) nested.They somehow conflict.
As a workaround I've patched it to remove the
BottomSheetViewwrapping: https://github.com/valora-inc/wallet/blob/bbd0e39dcc1420a704fa866113994e9a20c3bfa4/patches/%40th3rdwave%2Breact-navigation-bottom-sheet%2B0.3.2.patchThis works pretty well for us, but we must ensure the screens use one of the Gorhom components.
I'm not sure about the "right" solution to avoid this patch. Here are possible options:
childrento see if one of them is a Gohrom componentBottomSheetViewLooking forward to finding a solution that will work for all users of this lib.