I'm showing a list of named gadgets. They have a simple MutableState<String> name property. I fetch the list of a gadgets from a "Repository". The names are update-able (that's why I made them observable). So if the name changes, my "row" automagically updates. Isn't compose just beautiful?
Where it's a bit complicated (for me) is that I want to sort the list by that name. If my app was the only one that could change the name, then it wouldn't be too bad. As a side effect of changing the name, I could some trigger a recomposition at the Column level. But it's a multi user system. So the update to the name field could come asynchronously. I don't want the repository to keep track of "sorting" the gadgets, because it's just a keyed map basically. Is there an idiomatic way to solve this sort of problem?