Unidirectional Data Flow and State Events (A Taste of MVI) 

Congrats

What is race condition?

@@codingwithmitch I guess this situation could be in the process of producing state without showing progress (disabling user interaction) on ui. An end user could trigger two events without waiting for the other to finish. Or the push notification could trigger another event and the producer had already processed another event. In this case state producers could produce and emit two states at the same time and also they want to edit the same shared object (prolly old emitted state) at the same time. I guess state producer should work with flow or Mutex these cases to avoid a race condition. But i'm trying to find the best way to solve the problem. Btw they known as state reducer

@@gokberkyagc4442 For one shot properties (snackbars, dialogs, toasts) I like to build a stack of "pending messages". When the user clicks "ok" or the message goes away, it is removed from the stack. If I am understanding your "Race condition" question, you are essentially asking: "how can I do multiple requests/events at once and prevent one result from overriding another result?" I like to use flows that emit a common data structure. That data structure contains a field for each individual event response. So they can't overwrite one another. They are separate fields within the same encapsulating object

Prob never. But maybe play games on twitch 😬

I think it's waayyy better

Perfect