Hey there. Any tips on implementing a Compose Lazy...

# decompose

[s3rius]

Hey there. Any tips on implementing a Compose LazyList where every item of the list gets their own child component?

Since its conceptually similar to the Pages navigation I thought I'd start there, starting all children as DESTROYED and triggering creation/destruction via an Effect.
A big difference to other navigation types is that there would be more than one active child, so the concept of this being a "navigation" is kind-of gone now. So I'm not sure if the abstracting still fits.

[Arkadii Ivanov]

I think you would need to create your own navigation model: https://arkivanov.github.io/Decompose/navigation/children/overview/

Something named e.g. Child Items, like ComponentContext.childItems(...).