Found a strange behavior in `LazyColumnFor`. When ...

# compose

[Vsevolod Ganin]

Found a strange behavior in LazyColumnFor. When I use positional remember inside itemContent, it remembers everything for that particular index in the list. So when I remove an item in the source list, the (index + 1) item takes its place and inherits the memory of its predecessor. I think that’s because of the usage of key(index) in LazyColumnFor implementation. Is this intended?

[Vsevolod Ganin]

A small repro

@Preview
@Composable
fun Repro() {
    val list = remember { mutableStateListOf("a", "b", "c", "d", "e") }
    LazyColumnForIndexed(items = list) { index, item ->
        val randomNumber = remember { Random.nextInt(0..1000) }
        Text(
            text = "$item: $randomNumber",
            modifier = Modifier.clickable(onClick = {
                list.removeAt(index)
            })
        )
    }
}

[Vsevolod Ganin]

Using key(item) inside itemContent makes it behave as I wanted

[Zach Klippenstein (he/him) [MOD]]

Seems like a bug to me too, that behavior is really surprising. I’d just go ahead and file a bug.

[Vsevolod Ganin]

https://issuetracker.google.com/171230892