Advanced Concepts

MvRxViewModel

Constructor Dependency Injection

MvRx supports adding dependencies via constructor injection. To leverage this, create a companion object in your ViewModel and have it implement MvRxViewModelFactory<YourState>. That will force you to implement a create function. It will pass in the FragmentActivity that hosts the fragment. You should use that, if needed, to get or create your dagger/DI component and inject what you need. DO NOT pass a reference of your activity to your ViewModel. It will leak your Activity. Pass the application context if you must.

The code looks like this:

class MyViewModel(
    override val initialState: MyState, 
    private val repository: MyRepository
) : MvRxViewModel<MyState>() {
    ...
    companion object MvRxViewModelFactory<MyState> {
        override fun create(activity: FragmentActivity, state: MyState): BaseMvRxViewModel<MyState> {
            val repository: MyRepository by activity.inject()
            return MyViewModel(state, repository)
        }
    }
}

And we use this pattern in the sample app here.

Subscribing to state manually.

You can subscribe to state changes in your ViewModel. You may want to do this for logging, for example. This usually done in the init { ... } block. You can subscribe to state changes with:

subscribe { state -> }

subscribeWithHistory { oldState, newState -> }

subscribe(shouldUpdate = onSuccess(YourState::asyncProp)) { state -> }

MvRx comes with a few shouldUpdate helpers out of the box including:

• onSuccess: Calls the subscriber when an Async state property transitions from non-Success to Success.
• propertyWhitelist: A vararg of state properties to monitor for updates.

selectSubscribe(YourState::propA) { a -> }
selectSubscribe(YourState::propA, YourState::propB, YourState::propC) { a, b, c -> }

Debugging State

Call logStateChanges() in the init of your ViewModel and if debugMode is set to true, it will log all state changes to logcat. Assuming your state class is a Kotlin data class, the toString() should be readable.

Pagination

A successful pattern for pagination has been to have one state property store Async<List<T>> while another stores List<T>. The Async property contains the network request of the current page. This can be checked to prevent us from requesting duplicate pages simultaneously and can be queried to determine whether or not to show a loading indicator. The reducer for the pagination request should append results to the results list if it is successful like:

MvRxReviewsRequest.create(1234, offset).execute {
    copy(reviews = reviews.appendAt(it()?.reviews, offset), reviewRequest = it)
}

MvRx also includes appendAt to replace everything after the specified offset with the results. It handles edge cases like ignoring appending null and handling index out of bounds issues.

Dependent Requests

If you have an async request that is dependent on another, execute them like this:

/* In ViewModel */
init {
    onSubscribe(onSuccess(MyState::request1)) {
        fetchRequest2()
    }
}

Logging State Changes

You can log all state changes to logcat with logStateChanges

MvRxView

Subscribing to state manually.

You can subscribe to state changes in your View. You may want to do this for logging, for example. You can subscribe to state changes with:

viewModel.subscribe { state -> }

viewModel.subscribeWithHistory { oldState, newState -> }

viewModel.subscribe(shouldUpdate = onSuccess(YourState::asyncProp)) { state -> }

MvRx comes with a few shouldUpdate helpers out of the box including:

• onSuccess: Calls the subscriber when an Async state property transitions from non-Success to Success.
• propertyWhitelist: A vararg of state properties to monitor for updates.

selectSubscribe(YourState::propA) { a -> }
selectSubscribe(YourState::propA, YourState::propB, YourState::propC) { a, b, c -> }

MvRxState

Lists

You should use Kotlin's overloaded List operators to create new immutable lists like this:

setState { copy(yourList = yourList + it()) }

Maps

Use custom copy and delete extension functions and treat them similar to data classes:

setState { copy(yourMap = yourMap.copy(“a” to 1, “b” to 2)) }

or

setState { copy(yourMap = yourMap.delete(“a”, “b”)) }