A modern programming language that makes developers happier.

kotlinlang

Hey I have a stateflow for pending file uploads in a viewmodel like this:
```val uploadFlow = MutableStateFlow&lt;List&lt;UploadState&gt;&gt;(emptyList())```
And then each these UploadState object has another stateflow inside of it, is it safe if I use collectAsState e.g. in the MainScreen for the uploadFlow and then the corresponding stateflow from the uploadstate in their composable component? Or is that bad?

Your UI state (List&lt;UploadState&gt;) should be immutable and not contain other mutable state (like a StateFlow). I would suggest combining the UploadState flows in a single StateFlow of immutable UI states, and expose that to the UI layer

Not sure how I'd do that, how do I convert a List of flows (of a state) then to one flow?
So like: Flow&lt;List&lt;Flow&lt;State&gt;&gt;&gt; to Flow&lt;List&lt;State&gt;&gt;

Hello Ian. What’s the necessity of the second flow? If you want to notify the UI you should just change the first state. Just add whatever you’re sending in the second flow to the class you’re setting on the state. It won’t be a list, you’ll just emit a new state instead 

Flow list flow state, you can use flatten()