I have encountered a strange occurrence with `swip...
# compose
a
I have encountered a strange occurrence with
swipeableState
and
Modifier.swipeable
. I would like to confirm If I am missing something before filing a bug. Code in 🧵
For some reason, swipeable state does not reflect the initial value and had the padding start at the proper anchor's value. This changes when I call
Copy code
println("${swipeAbleState.targetValue}")
As soon as this line enters the composition, the swipeableState reflects it's starting anchor and sets the padding to 48. I am unsure as to why this triggers the state to be taken into effect, as the default behavior should be that the initial state begins at the proper anchor when it gets created in the first composition.