Vairavan Srinivasan

@jshvarts Even though it works, that approach leads to some tightly coupled design. UI needs to be aware of the source which can influence the data like network etc. A...

Not a redux implementation per se but Room's LiveData update is an example. It doesn't matter how the data was updated in the database (network/UI or other background tasks), all...

@Glurt Just FYI. Trying to relay navigation update as event/effect (SingleLiveEvent) fails in an edge case with lifecycle and fragment transactions. https://github.com/kaushikgopal/movies-usf/issues/19

> This seems like a good way to handle single events https://ryanharter.com/blog/handling-transient-events/ events can be dispatched from within bindActions() Checked it, the subscription until onDestroy still has the same problem...

Not to mention, canceling the task onPause and restart onResume is a no go.

In my case, it is scoped to pause and resume. However re-subscribing from onResume is no good as the effect observable has no cache/replay behavior (in the case where task...

> I was just poking around the Roxie github page so forgive me if I'm way off on what you're trying to accomplish, but would this suit your purpose? >...

It works with the new version of mockito-kotlin, testCompile 'com.nhaarman.mockitokotlin2:mockito-kotlin:2.0.0'

> Hi @garispe , Thanks for reaching out on this and for the PR. > > The event listeners mentioned [here](https://firebase.google.com/docs/in-app-messaging/modify-message-behavior?platform=android#implement_an_event_listener_for_card_interactions) are for the purpose of tracking the user interactions...

Any luck on this one?