<https://developer.android.com/jetpack/compose/lis...
# composea
allan.conda
07/27/2021, 8:55 AMhttps://developer.android.com/jetpack/compose/lists#item-keys
Is it preferable to always provide stable keys when available, or are there downsides to using it?
h
Halil Ozercan
07/27/2021, 9:01 AMI'd say there is really no downside to using key when available. To understand it better I'd recommend checking this thread out. Key concept is very similar in React and Jetpack Compose.
a
allan.conda
07/27/2021, 9:05 AMI see. Thank you, I’ll check it out
c
cb
07/27/2021, 9:05 AMYes, it’s preferable to always provide a key
h
hfhbd
07/27/2021, 9:10 AMIf it is preferable, why does compose do not require them, like SwiftUI with Identifiable?
a
allan.conda
07/27/2021, 9:12 AMI just discovered it, actually, I’ve never used it in my LazyColumn. I just saw it recently in the changelog and it’s about adding the support for the Paging Items.
c
Colton Idle
07/27/2021, 2:40 PMSuch a great thread @Halil Ozercan 💯
c
cb
07/28/2021, 7:09 AMKeys were a late addition to the LazyList DSL so I don’t believe there was a way to make them mandatory at the time.
@Andrey Kulikov
a
Andrey Kulikov
07/28/2021, 10:21 AMthere are some limitations with keys - the value you provide should be saveable into a Bundle, plus keys should be unique between all the elements in the list. when you don’t provide a key then indexes are used as keys internally
👍 1
c
Colton Idle
07/28/2021, 2:04 PMIndexes as a fallback makes sense. A lint rule for this would be great I think though.
Colton Idle
07/28/2021, 2:06 PMFiled a FR for a lint rule: https://issuetracker.google.com/issues/194822807
6 Views