Let’s say I have a `data class` object: ```val sta...

# getting-started

[Daniele B]

Let’s say I have a data class object:

val state : AppState = AppState()

where:

data class AppState (
  val loginState : LoginState = LoginState(),
  val showingDetail : Boolean = false,
)
data class LoginState (
  val loginVar : String
)

if I want to just change a child property, it’s very simple, it just takes 1 line:

state = state.copy(showingDetail = true)

but it I want to change the property of one child, I need 3 lines:

var login = state.loginState
login = login.copy(loginVar = "my value")
state = state.copy(loginState = login)

is there a simpler syntax to achieve this?

[Tobias Berger]

I mean, you could do the same in a single line:

state = state.copy(loginState = state.loginState.copy(loginVar = "my value"))

I'm just not sue if that makes it better

[Tobias Berger]

If you want to keep your objects immutable and want to change something on a deeper level, there is probably no other way than cascading through the structure like that. Of course you could implement additional function to hide that complexity.

[Tobias Berger]

just to be a bit creative: you could also write it like this:

state = state.run { copy(loginState = loginState.copy(loginVar = "my value")) }

[Daniele B]

I am was looking into writing additional functions.
Ideally I would like to update an inner object with a function like this:

updateLoginState(loginVar = "my value")

but I don’t know how to write a function that, which takes the same arguments of copy

[Daniele B]

fun updateLoginState (I DON'T KNOW HOW TO DEFINE THE ARGUMENTS) {
	var login = state.loginState
	login = login.copy(ARGUMENTS)
	state = state.copy(loginState = login)
}

[Tobias Berger]

there is no way to automatically do that, so you will just have to write them explicitly, like any other function parameter

[Daniele B]

so, is copy a very special function?

[Tobias Berger]

it's not special, it's just automatically generated...

[Daniele B]

so, I guess the Kotlin language doesn’t allow similar functionality for custom functions

[Tobias Berger]

the generated copy of you LoginState would look like this:

data class LoginState (
  val loginVar : String
) {
  fun copy(loginVar: String = this.loginVar) : LoginState { 
    return LoginState(loginVar)
  }
}

[Daniele B]

thanks, interesting to visualize that

[Tobias Berger]

If you want that updateLoginState functionality (esp. if LoginState has multiple properties instead of just one) you can implement it manually, but it will not be automatically generated and if you change the class, you will have to update the method yourself

[Daniele B]

yes, I am trying to think what would be the simplest syntax to make updates on an object like LoginState

[Tobias Berger]

so you could write

fun AppState.updateLoginState (loginVar: String = loginState.loginVar) {
	state = state.copy(loginState = LoginState(loginVar))
}

[Tobias Berger]

the key is to use the current values of the current loginState as defaults for the optional function parameters

[Daniele B]

yes, I would need to manually generate that, though, which would not be feasible in case there are many properties

[Daniele B]

thanks anyway, you made me think

[Daniele B]

👍

[Tobias Berger]

many properties aren't really a problem if they don't change at all.
You could also consider if you really need immutability. I know it's generally considered good practice, but in some cases it just makes things more complicated without bringing any actual benefits

[Daniele B]

I need to pass the state via StateFlow

[Daniele B]

so, I think it would need to be immmutable

[Daniele B]

especially I know there are immutability issues with Kotlin/Native

[Daniele B]

And I am expecting Jetpack Compose to also wanting immutable objects?

[Tobias Berger]

I haven't really worked on any real android projects for years so I can't tell you anything about that. If you need immutability that's fine, just wanted to make sure you considered it.

[Daniele B]

At the moment, the simplest I am able to do is:

updateLoginState(state.loginState.copy(loginVar = "my value"))

I would like to be able to do like this:

updateLoginState(loginVar = "my value")

but it’s not the end of the world

[Daniele B]

my current updateLoginState()
function is this one:

fun updateLoginState(loginState: LoginState) {
        state = state.copy(loginState = loginState)
    }

[Tobias Berger]

why not this?

fun updateLoginState(loginVar: String) {
        state = state.copy(loginState = state.loginState.copy(loginVar = loginVar))
    }

Sure, that's the manual implementation again. But personally I'd prefer that rather than doing the copy outside.

[Adam Powell]

You might be interested in arrow's optics features: https://arrow-kt.io/docs/optics/lens/