I have a list used in a `LazyColumn` and a corresp...

# compose-desktop

[S.]

I have a list used in a LazyColumn and a corresponding add function in the viewmodel but no matter what I try the list does not refresh itself.
basically the same code is used for a search feature which works fine. only difference it's not called from a onClick but from onValueChanged

[S.]

Screen:

val decks by viewModel.decks.collectAsState()

ViewModel

private val _decks = MutableStateFlow(Client.userDecks.value)
    val decks: StateFlow<List<Deck>> = _decks

    suspend fun addDeck(deck: NewDeck) {
        Client.addDeck(deck)
        _decks.value = Client.userDecks.value
    }

    suspend fun filterDecks(input: String) {
        _decks.value = Client.userDecks.value.filter { bla bla }
    }

[S.]

also checked with printing _decks.value and it does contain the added value. forcing the list to recompose by switching screens etc also shows the new value

[Albert Chang]

What is Client.userDecks?

[S.]

StateFlow<List<Deck>> , Deck being a custom data class

[Albert Chang]

What does Client.addDeck() do?

[S.]

POST api call and then adding given deck to userDecks as well

[S.]

well, actually to the MutableStateFlow of it. just checked

[S.]

private val myDecks = MutableStateFlow<MutableList<Deck>>(mutableListOf())
val userDecks: StateFlow<List<Deck>> = myDecks

[Albert Chang]

https://dev.to/zachklipp/two-mutables-dont-make-a-right-2kgp

[S.]

I will check it tomorrow, seems promising ty

[S.]

I'm using the StateFlow inside Client for a superordinate side menu that's supposed to always show, hence my rather scuffed code there. we'll see

[Michael Paus]

Probably not directly related to your problem but this line in your ViewModel

val decks: StateFlow<List<Deck>> = _decks

should more correctly be

val decks: StateFlow<List<Deck>> = _decks.asStateFlow()

[S.]

So the issue was indeed the mutable, ty again.
(also makes totally sense)

but shouldn't asStateFlow() be the same as writing the type explicitly?

[Mitchell Syer]

asStateFlow blocks even casts from working. If you just write the type explicitly then it can be casted to a MutableStateFlow again.