When the user taps the FAB on the event details to toggle an event's status as favourite, the button should immediately reflect the resulting model change. Due to current architectural constraints, the process which changes this state uses its own RootDb instance, circumventing the subscription by the fragment to changes on its own instance, thus requiring the ui to proactively predict which state the model will be in, provided the action triggered by the user interaction will be persisted successfully.
It's not a nice solution, but for the time being, I'd file it under #WorksForMe, especially since a proper fix would probably require major restructuring.
When the user taps the FAB on the event details to toggle an event's status as favourite, the button should immediately reflect the resulting model change. Due to current architectural constraints, the process which changes this state uses its own RootDb instance, circumventing the subscription by the fragment to changes on its own instance, thus requiring the ui to proactively predict which state the model will be in, provided the action triggered by the user interaction will be persisted successfully.
It's not a nice solution, but for the time being, I'd file it under #WorksForMe, especially since a proper fix would probably require major restructuring.