Question about the usage of internal APIs in the bottom sheet implementation

[StylianosGakis]

This is not a feature request nor a bug report, I was mostly curious about the lines I can see inside here in particular

FlexibleBottomSheet/flexible-core/src/androidMain/kotlin/com/skydoves/flexible/core/FlexibleBottomSheetPopup.kt

Lines 182 to 191 in 688b8f7

	val className = "android.view.WindowManager\$LayoutParams"
	val layoutParamsClass = Class.forName(className)
	val privateFlags: Field = layoutParamsClass.getField("privateFlags")
	val noAnim: Field = layoutParamsClass.getField("PRIVATE_FLAG_NO_MOVE_ANIMATION")
	var privateFlagsValue: Int = privateFlags.getInt(this)
	val noAnimFlag: Int = noAnim.getInt(this)
	privateFlagsValue = privateFlagsValue or noAnimFlag
	privateFlags.setInt(this, privateFlagsValue)

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?

[skydoves]

Hey @StylianosGakis, sorry for the late response. That's an interesting question. Yes, the FlexibleBottomSheet uses reflection to access private fields in WindowManager. However, you don't need to worry about it, as the code in WindowManager has remained unchanged for 13 years 😄, as you can see in the AOSP:
https://android.googlesource.com/platform/frameworks/base/+log/539ee87/core/java/android/view/WindowManager.java