why not add a new key world observable to kotlin

data class ObservableFieldProfile(
        val name: String,
        val lastName: String,
        val likes: ObservableInt
)

to reduce such long meaningless name into

observable FieldProfile (
        val name: String,
        val lastName: String,
        val likes: Int
)

Doesn’t make sense to me. First example here is just naming the object “observable “ but it’s not even observable. It’s just a data class

why it is named ObservableFieldProfile if it is not an observable data ?

FYI. that

observableFieldsActivityButton

is derived form the

id

of the view in the xml. you can name it whatever you want.

You should tell the example builder to learn a good naming skill to avoid such misunderstanding.

It’s a good name in my opionion - it’s the button the open the Observable Field Activity 😅 couldn’t be less expressive 😂

Maybe Christian Grach Observable Field Activity is a much cheaper name.

Why so ovensive? I just try to give you feedback why someone is doing something that you did not understand in the first place.

I just try to follow your logic to understand what is less expensive.

What you mean with expensive? How would a meaningful name be “expensive”

I don’t see how it’s more clear when a field is declared with the type it is. You can also use Kotlin delegation to make all fields observable, or the usage of the data class as observable itself

why not just have a keyword for everything? Surely that would help?

class observable field profile

> why not add a new key world observable to kotlin It's already in the standard library:

var value: Int by Delegates.observable { p, old, new ->
    println("The value changed: $old -> $new")
}

https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.properties/-delegates/observable.html