Passing keys all round is very inconvenient and error prone, is there a better way to perform item list recompositions?

could you please explain a bit more what you currently have and what you don’t like about it? thanks

Mostly errors that I see, is when some outer to LazyColum state changes, and then accidentally used within item, which results in wrong positional memoization Like:

@Composable
fun CCaller() {
    var list by remember { mutableStateOf<List<CartItem>>(listOf()) }
    
    CComposable(list = list, onRemove = { 
        list = list - list.last()
    })
}

@Composable
fun CComposable(list: List<CartItem>, onRemove: () -> Unit) {
    LazyColumn {
        items(list) {
            Box(Modifier.pointerInput(it) { 
                this.detectDragGestures(
                    onDragEnd = { onRemove() },
                    onDrag = { _, _ -> }
                )
            })
        }
    }
}

does this bug looks like the same issue as you experience? https://issuetracker.google.com/issues/163069767

No, problem here is that onRemove within pointerInput not get recomposed, and by this containing old list, for items that doesn't changed

oh, yes, it is what you need. you will need it regardless of LazyColumn

Sure, and that's I find a problem, because in my case

Box(Modifier.pointerInput(it) { 
                this.detectDragGestures(
                    onDragEnd = { onRemove() },
                    onDrag = { _, _ -> }
                )
            })

Was deep in sub components And that's why it was very hard to debug and fix such problems, and a reason I asking

I agree with you that probably some lint rule for Modifier.pointerInput() for cases like this can help with fixing such issues

Is there any open issue for that?

from what I aware no, feel free to file one

@semoro Would you since you have all the details on the use case? I'll star it.

But still, why it is not recomposed automatically?

it is not about not recomposing. what you pass to Modifier.pointerInput is a suspend function. we can’t just restart it automatically, so you have to provide a hint on when something really important for the function has been changed. see more details in the kdocs: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]tFilter.kt;l=120;drc=07e0987038a2d1792fcd98944c79e7ae775a6eb5

The link points to a constant, not a KDoc 🤔

yeah, it is a error used in the intentionally deprecated method. anyway, I meant this and the docs on the method itself