Silly question, but I believe, basic discipline like that adds up to cleaner code… I have data class...

# announcements

[Jakub]

Silly question, but I believe, basic discipline like that adds up to cleaner code…
I have data class that should be called List. How would you name that class?

[Rachid]

What types would you store in that list?

[Jakub]

this is my Entity something like

data class List_(
    val uuid: String = UUID.randomUUID().toString(),
    val name: String = "",
    val entries: List<Entry> = emptyList()
)

I’m calling it List_ but smells a bit

[Rachid]

I won't call it List since that's already an existing type. I would add something to the name that makes it clear what makes this data class different than the existing kotlin.collections.List

[David Eriksson]

Lists and Entry... so very generic... but maybe EntryList then 🙂

[Rachid]

I won't prefer such generic names either, but agree with David..

[Rachid]

Or NamedList, because this is a List with a Name

[Rachid]

data class NamedList<T>(
    val uuid: String = UUID.randomUUID().toString(),
    val name: String = "",
    val entries: List<T> = emptyList()
)

[Jakub]

Hah, after working for a big company where names were like NamedWithEntriesAndAttachedList I’m just so much in love with short names that are not noisy. But drawbacks are when you wanna refactor it in IDE and sometime names conflicts like now 😉

[Jakub]

Will go for ShoppingList Cheers guys!

[Rachid]

Yeah, that sounds like a meaningful name ;)

[Jakub Pi]

There are two great problems in Computer Science. Naming things, cache invalidation, and off by one errors.\