Last active
February 3, 2023 19:08
-
-
Save magneticflux-/044c9d7a3cea431aa0e4f4f4950a2898 to your computer and use it in GitHub Desktop.
Helpful Android-Kotlin LiveData utilities
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
//-------------------------------- | |
// CHECK THE COMMENTS FOR UPDATES! | |
//-------------------------------- | |
/* | |
* Copyright (C) 2017 Mitchell Skaggs, Keturah Gadson, Ethan Holtgrieve, Nathan Skelton, Pattonville School District | |
* | |
* This program is free software: you can redistribute it and/or modify | |
* it under the terms of the GNU General Public License as published by | |
* the Free Software Foundation, either version 3 of the License, or | |
* (at your option) any later version. | |
* | |
* This program is distributed in the hope that it will be useful, | |
* but WITHOUT ANY WARRANTY; without even the implied warranty of | |
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | |
* GNU General Public License for more details. | |
* | |
* You should have received a copy of the GNU General Public License | |
* along with this program. If not, see <http://www.gnu.org/licenses/>. | |
*/ | |
import android.arch.lifecycle.LiveData | |
import android.arch.lifecycle.MediatorLiveData | |
import android.arch.lifecycle.Transformations | |
/** | |
* This function creates a [LiveData] of a [Pair] of the two types provided. The resulting LiveData is updated whenever either input LiveData updates and both LiveData have updated at least once before. | |
* | |
* If the zip of A and B is C, and A and B are updated in this pattern: `AABA`, C would be updated twice (once with the second A value and first B value, and once with the third A value and first B value). | |
* | |
* @param a the first LiveData | |
* @param b the second LiveData | |
* @author Mitchell Skaggs | |
*/ | |
fun <A, B> zipLiveData(a: LiveData<A>, b: LiveData<B>): LiveData<Pair<A, B>> { | |
return MediatorLiveData<Pair<A, B>>().apply { | |
var lastA: A? = null | |
var lastB: B? = null | |
fun update() { | |
val localLastA = lastA | |
val localLastB = lastB | |
if (localLastA != null && localLastB != null) | |
this.value = Pair(localLastA, localLastB) | |
} | |
addSource(a) { | |
lastA = it | |
update() | |
} | |
addSource(b) { | |
lastB = it | |
update() | |
} | |
} | |
} | |
/** | |
* This is merely an extension function for [zipLiveData]. | |
* | |
* @see zipLiveData | |
* @author Mitchell Skaggs | |
*/ | |
fun <A, B> LiveData<A>.zip(b: LiveData<B>): LiveData<Pair<A, B>> = zipLiveData(this, b) | |
/** | |
* This is an extension function that calls to [Transformations.map]. | |
* | |
* @see Transformations.map | |
* @author Mitchell Skaggs | |
*/ | |
fun <A, B> LiveData<A>.map(function: (A) -> B): LiveData<B> = Transformations.map(this, function) | |
/** | |
* This is an extension function that calls to [Transformations.switchMap]. | |
* | |
* @see Transformations.switchMap | |
* @author Mitchell Skaggs | |
*/ | |
fun <A, B> LiveData<A>.switchMap(function: (A) -> LiveData<B>): LiveData<B> = Transformations.switchMap(this, function) |
That's single time zip
which will behave as combineWith
once both value is not null. Here's updated version. I've also added dynamic result block.
fun <A, B, R> zipLiveData(
a: LiveData<A>,
b: LiveData<B>,
block: (A, B) -> R
): LiveData<R> {
return MediatorLiveData<R>().apply {
var lastA: A? = null
var lastB: B? = null
fun update() {
val localLastA = lastA
val localLastB = lastB
if (localLastA != null && localLastB != null) {
this.value = block.invoke(localLastA, localLastB)
lastA = null
lastB = null
}
}
addSource(a) {
lastA = it
update()
}
addSource(b) {
lastB = it
update()
}
}
}
fun <A, B, R> LiveData<A>.zipWith(b: LiveData<B>, block: (A, B) -> R): LiveData<R> = zipLiveData(this, b, block)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@friederbluemle
lastA
andlastB
are mutable and nullable, so their contents can change at any time due to multithreaded code.localLastA
andlocalLastB
are immutable and nullable, so their contents are fixed and can be asserted in sequence (localLastA != null && localLastB != null
) without possibility oflocalLastA
changing after evaluation. It's all so that there's no possibility of a null slipping through, even in concurrent code.