I have found myself writing some snippets similar to this. Is there a better way to do it? ```fun u...

# getting-started

[Colton Idle]

I have found myself writing some snippets similar to this. Is there a better way to do it?

fun updateUser(username: String? = null, email: String? = null, token: String? = null) {
  if (username != null) {
    _appUser.value = _appUser.value?.copy(username = username)
  }
  if (email != null) {
    _appUser.value = _appUser.value?.copy(email = email)
  }
  if (token != null) {
    _appUser.value = _appUser.value?.copy(authToken = token)
  }
}

[ephemient]

you could do just one copy,

if (username != null || email != null || token != null) (
    val appUser = _appUser.value
    _appUser.value = appUser.copy(
        username = username ?: appUser.username,
        email = email ?: appUser.email,
        authToken = token ?: appUser.authToken,
    )
}

[Colton Idle]

Cooll. okay so not far off from what i had. thanks!

[Francesc]

If _appUser is a mutable state flow, consider using the update extension function to update it

[itzik kasovitch]

You can use the let extension to get rid of the if something is null check

[itzik kasovitch]

https://www.journaldev.com/19467/kotlin-let-run-also-apply-with

[Colton Idle]

_appUser IS a mutablestateflow!