🐬 Advanced Compose Multiplatform bottom sheet for segmented sizing, non-modal type, and allows interaction behind the bottom sheet similar to Google Maps.
Apache License 2.0
687
stars
30
forks
source link
Question about the usage of internal APIs in the bottom sheet implementation #36
I am only asking because I am concerned about what kind of risks you think one would be opting into while using this. And what are the chances that these private APIs will change in the future in a backwards incompatible way making this not work as expected in future Android API levels. If that were to happen, can the library update the code accordingly to keep all of this working as expected?
This is not a feature request nor a bug report, I was mostly curious about the lines I can see inside here in particular https://github.com/skydoves/FlexibleBottomSheet/blob/688b8f716c3828a5eb1871f5c14ddba7d96f9037/flexible-core/src/androidMain/kotlin/com/skydoves/flexible/core/FlexibleBottomSheetPopup.kt#L182-L191
I am only asking because I am concerned about what kind of risks you think one would be opting into while using this. And what are the chances that these private APIs will change in the future in a backwards incompatible way making this not work as expected in future Android API levels. If that were to happen, can the library update the code accordingly to keep all of this working as expected?