Resource

Handy states for dynamically obtained data.

Table of contents

• Problem to solve
• Reasons to use
• Artifacts
  • resource-plain
  • resource-context
• Installation
• Example of usage
• License

---

Problem to solve

In contemporary software development a huge number of operations and their results are asynchronous. Imagine, you're obtaining a data from a local storage. Let's say, you've created some kind of Observable and now observe its value, which is initially null. Next you trigger fetchData() and wait.

Five seconds have passed, but value is still null. What does it mean? Was there some error? Was the result null? Or connection is still being established, and you have nothing to worry about?

This is where Resource kicks in.

It represents some explicit state of dynamically obtained data. For instance, it could be Empty , Loading, Success or Failure state, where Success carries obtained data and Failure encapsulates exception cause.

Besides, Resource is a highly customizable state machine and may be used as a flexible tool for managing state.

Reasons to use

1. Concept is easy to understand.
2. Library is pleasant to use: it's extendable, customizable and has a lot out-of-the-box features.
3. Implementations of Resource are immutable, which makes them a great choice to use with such solutions like Kotlin Flow and Android LiveData.
4. Small source code size.
5. 100% documented.

Artifacts

resource-plain

com.github.mmolosay.resource:resource-plain:VERSION

Sealed implementation of Resource with only Resource.Empty, Resource.Loading, Resource.Success and Resource.Failure derived states. Sealing makes it exhaustive in when statement, thus it's easy to cover all cases of actual instance. Note: author recommends to use Resource.invoke() extension function instead of when expression.

resource-context

com.github.mmolosay.resource:resource-context:VERSION

Philosophy of this artifact allows you to customize a context, in which your Resource states will change.

For example, you may want your resource to only have states of Empty and Success (ReducedScope), when you're interested in data or its absence only. You will be given scope, in which you can create states for resource: it will protect you from setting state out of context.

See Example of usage section for more details.

Installation

Use JitPack to add it as a dependency to your Kotlin project. Code snippet below shows way for adding it via Gradle Kotlin DSL:

repositories {
    mavenCentral()
    maven("https://jitpack.io") // make sure to use jitpack repository
}

dependencies {
    implementation("com.github.mmolosay.resource:ARTIFACT:VERSION")
}

Where:

• ARTIFACT is a desired implementation. See Artifacts section for more details.
• VERSION is the version of desired release. It can be obtained on releases page. Latest release version is stated at the top of this document in JitPack badge.

Example of usage

Following simplified examples demonstrate a way to use Resource flavors with Kotlin Flows:

resource-plain

Full sample is in sample.resource-plain module.

// Declare your resource flow
val flow = MutableStateFlow(Resource.empty<YourData>())
...
// Change values
fun getData() {
    flow.update { Resource.loading() }
    try {
        getDataAsync { data ->
            flow.update { Resource.success(data) }
        }
    } catch (e: SomeException) {
        flow.update { Resource.failure(e) }
    }
}
...
// Observe changes
flow.collect { resource ->
    resource.invoke(
        onEmpty = { /* update UI, like showing some message */ },
        onLoading = { /* update UI, like showing progress bar */ },
        onSuccess = { data -> /* populate data to UI */ },
        onFailure = { cause -> /* display notification on UI */ }
    )
}

resource-context

Full sample is in sample.resource-context module.

// Declare your resource flow
val flow = MutableStateFlow(resource<YourData>()) // empty by default
...
// Change values
fun getData() {
    flow.update { it with { loading() } }
    try {
        getDataAsync { data ->
            flow.update { it with { success(data) } }
        }
    } catch (e: SomeException) {
        flow.update { it with { failure(e) } }
    }
}
...
// Observe changes
flow.collect { resource ->
    // You can use provided extension or write your own for your custom states
    resource.invoke(
        onEmpty = { /* update UI, like showing some message */ },
        onLoading = { /* update UI, like showing progress bar */ },
        onSuccess = { data -> /* populate data to UI */ },
        onFailure = { cause -> /* display notification on UI */ }
    )
}

License

Copyright 2022 Mikhail Malasai

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.