Is there a reason why I shouldn’t put the `SnackbarHostState` in the `ViewModel`? Seems like an unne...

# compose

[Alex]

Is there a reason why I shouldn’t put the SnackbarHostState in the ViewModel? Seems like an unnecessary dance to from event -> state -> lambda in compose -> snackbarhoststate (which internally converts the event into a state again) -> callback to viewmodel that the state was “consumed”.
Using viewModelScope to launch the snackbar would just suspend the launch call until the view is available it seems.. which is fine?

[Stylianos Gakis]

Just do it. It’s not uncommon to hoist some state holder classes up there, like TextFieldState for example.

[Francesc]

the way I think about it is, "does the viewmodel need to know about this?" If so, put it in the viewmodel, otherwise leave it in the compostable usually as a stateholder.

[Tobias Preuss]

Testing?

[Alex]

It will live behind an injected interface @Tobias Preuss so testing won’t be an issue

[Alex]

My intention is to avoid the dance from viewmodel -> state“event“ -> event -> back to state in snackbarhoststate

[Tobias Preuss]

😶‍🌫️ I can't really judge. I have not used SnackbarHostState myself.

[Alex]

You will cross paths with it I promise you haha