Marcin Wisniowski
06/04/2023, 4:35 PMrememberRipple()
, for passing into Modifier.clickable(indication = ...)
. Where did it go?Stylianos Gakis
06/04/2023, 4:44 PMLocalIndication.current
if you want the one provided by the material theme, since I see it passes it in that place which I linked to you.Marcin Wisniowski
06/04/2023, 5:12 PMandroidx.compose.material:material-ripple
doesn’t have an m3 equivalent, but not sure if there’s a need for such a thing to existThe thing is, if you use M3, you don't want to include the M2 dependency just to use a single thing from it.
Stylianos Gakis
06/04/2023, 5:26 PMThe thing is, if you use M3, you don’t want to include the M2 dependency just to use a single thing from it.Yeah I absolutely agree. I haven’t looked into it since we’re using both themes right now (and will be for a long time as I see it) so I haven’t tried to see what’s left in order to drop the dependency completely. But yes, sounds like pull to refresh should be similarly pulled out of the core material dependency just like material-ripple is. You could make a bug report (If no similar bug exists) if you have the time, I’d love to upvote it to see what google thinks about this.
raenardev
06/05/2023, 1:43 PM...
*/
// TODO(b/244423199): Move pullRefresh into its own material library similar to material-ripple.
@ExperimentalMaterialApi
fun Modifier.pullRefresh(
state: PullRefreshState,
enabled: Boolean = true
) = inspectable(inspectorInfo =
...