why not add a new key world observable to kotlin `...

# android

[calidion]

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
)

[agrosner]

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

[agrosner]

You want all fields individually observable?

[calidion]

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

[calidion]

You should ask android team why made it observable first.

[Chrimaeon]

FYI. that observableFieldsActivityButton is derived form the id of the view in the xml. you can name it whatever you want.

[Chrimaeon]

and it has nothing to do with observables. you should check the tutorial you are refering to a little bit deeper.

[calidion]

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

[Chrimaeon]

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

[calidion]

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

[Chrimaeon]

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

[calidion]

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

[Chrimaeon]

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

[agrosner]

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

[kevin.cianfarini]

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

class observable field profile

[kevin.cianfarini]

Oh no….compiler error:

e: observable can only be called from the context of an observable identifier, field is not observable

[kevin.cianfarini]

🧌

[CLOVIS]

> 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