A modern programming language that makes developers happier.

kotlinlang

For one-shot events in Jetpack Compose (with MVIKotlin + Decompose) is the best way to fire two Intents/Labels? The first setting a flag in the Model, second undoing it? I can't figure out how to get Compose to recognize the same event twice otherwise but I see issues down the line with this workaround.

Ex:
```Intent.ShowThing -&gt; State(showThing = true), Intent.SomeOtherAction -&gt; State(showThing = true),
Intent.HideThing -&gt; State(showThing = false)```

What you mean by "recognize the same event twice"?

If I create a variable in the model for one time events :
```val viewActions: Value&lt;ViewActions&gt; ```

Where ViewActions is a sealed class
```sealed class ViewActions{
object ShowSnackbar: ViewActions()
}```

the first time I set that value, the event will fire but the second time it does not. Because it is an object compose doesn't care it has been set twice? It detects the same value and doesn't recall the view function?

Searching for MVI related solutions generally seemed to be a mix of different workarounds

The `Value` thing is converted to Compose `State` for observations. I don't think it is a right way to deliver one time events. I think it has `equals` check somewhere under the hood. I would say that snack bar visibility should be either part of the state, or should be delivered via e.g. an `Observable` or a `Flow` . So you could subscribe for it in the UI layer. Or you can introduce your own `SnackBarController` and pass it to the `Component`.

makes a lot of sense there. I will dig into all three of those. Thanks for the point in the right direction

A simple observable subscription now. I'm looking into the Reaktive sources more to understand _what_ I'm doing here. I'm coming from Xamarin Forms for multiplatform so things are a bit different to say the least! I want to make sure I'm not leaking that subscription from the composable

You will be safe if you unsubsribe in onDispose {}. Also maybe worth to ask in <#CJLTWPH7S|compose> channel about any best practices.

I've been keeping my eye on that channel for recent updates as documentation on the web is all over the place, hah! I'll go back a bit and read up. As always, much appreciated on nudging in the right directions.