MediatorLiveData vs LiveData
up vote
0
down vote
favorite
I am not able to get the idea of MediatorLiveData while working with LiveData. In documentation it is mentioned that MediatorLiveData is a subclass of LiveData that will observe LiveData and react on onChanged
method. My question is what's it's difference from having a function in observe
of LiveData and do something with data if the new data is different?
For example, let's say I have query from Room Database that returns LiveData as below
@Query(“SELECT * FROM Users WHERE userid = :id”)
fun getUserById(id: String): LiveData<User>
If I want to use MediatorLiveData
, I can have an extension as below
fun <T> LiveData<T>.distinctUntilChanged(): LiveData<T>{
var lastValue: Any? = Any()
return MediatorLiveData<T>().apply {
addSource(this@distinctUntilChanged){
if (it != lastValue){
lastValue = it
postValue(it)
}
}
}
}
And then use it in my Activity as
userDao.getUserById("someId").distinctUntilChanged()
.observe(this, user -> {/*Do something with user*/})
Contrary to above scenario, I can just have a wrapper function inside observe
method as below
var lastUser = null
userDao.getUserById("someId")
.observe(this, user -> {
if (lastUser != user){
lastUser = user
/*Do something with user*/
}
})
Can anyone elaborate why I should use MediatorLiveData
instead of just having simple check?
kotlin android-room android-livedata kotlin-extension
add a comment |
up vote
0
down vote
favorite
I am not able to get the idea of MediatorLiveData while working with LiveData. In documentation it is mentioned that MediatorLiveData is a subclass of LiveData that will observe LiveData and react on onChanged
method. My question is what's it's difference from having a function in observe
of LiveData and do something with data if the new data is different?
For example, let's say I have query from Room Database that returns LiveData as below
@Query(“SELECT * FROM Users WHERE userid = :id”)
fun getUserById(id: String): LiveData<User>
If I want to use MediatorLiveData
, I can have an extension as below
fun <T> LiveData<T>.distinctUntilChanged(): LiveData<T>{
var lastValue: Any? = Any()
return MediatorLiveData<T>().apply {
addSource(this@distinctUntilChanged){
if (it != lastValue){
lastValue = it
postValue(it)
}
}
}
}
And then use it in my Activity as
userDao.getUserById("someId").distinctUntilChanged()
.observe(this, user -> {/*Do something with user*/})
Contrary to above scenario, I can just have a wrapper function inside observe
method as below
var lastUser = null
userDao.getUserById("someId")
.observe(this, user -> {
if (lastUser != user){
lastUser = user
/*Do something with user*/
}
})
Can anyone elaborate why I should use MediatorLiveData
instead of just having simple check?
kotlin android-room android-livedata kotlin-extension
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am not able to get the idea of MediatorLiveData while working with LiveData. In documentation it is mentioned that MediatorLiveData is a subclass of LiveData that will observe LiveData and react on onChanged
method. My question is what's it's difference from having a function in observe
of LiveData and do something with data if the new data is different?
For example, let's say I have query from Room Database that returns LiveData as below
@Query(“SELECT * FROM Users WHERE userid = :id”)
fun getUserById(id: String): LiveData<User>
If I want to use MediatorLiveData
, I can have an extension as below
fun <T> LiveData<T>.distinctUntilChanged(): LiveData<T>{
var lastValue: Any? = Any()
return MediatorLiveData<T>().apply {
addSource(this@distinctUntilChanged){
if (it != lastValue){
lastValue = it
postValue(it)
}
}
}
}
And then use it in my Activity as
userDao.getUserById("someId").distinctUntilChanged()
.observe(this, user -> {/*Do something with user*/})
Contrary to above scenario, I can just have a wrapper function inside observe
method as below
var lastUser = null
userDao.getUserById("someId")
.observe(this, user -> {
if (lastUser != user){
lastUser = user
/*Do something with user*/
}
})
Can anyone elaborate why I should use MediatorLiveData
instead of just having simple check?
kotlin android-room android-livedata kotlin-extension
I am not able to get the idea of MediatorLiveData while working with LiveData. In documentation it is mentioned that MediatorLiveData is a subclass of LiveData that will observe LiveData and react on onChanged
method. My question is what's it's difference from having a function in observe
of LiveData and do something with data if the new data is different?
For example, let's say I have query from Room Database that returns LiveData as below
@Query(“SELECT * FROM Users WHERE userid = :id”)
fun getUserById(id: String): LiveData<User>
If I want to use MediatorLiveData
, I can have an extension as below
fun <T> LiveData<T>.distinctUntilChanged(): LiveData<T>{
var lastValue: Any? = Any()
return MediatorLiveData<T>().apply {
addSource(this@distinctUntilChanged){
if (it != lastValue){
lastValue = it
postValue(it)
}
}
}
}
And then use it in my Activity as
userDao.getUserById("someId").distinctUntilChanged()
.observe(this, user -> {/*Do something with user*/})
Contrary to above scenario, I can just have a wrapper function inside observe
method as below
var lastUser = null
userDao.getUserById("someId")
.observe(this, user -> {
if (lastUser != user){
lastUser = user
/*Do something with user*/
}
})
Can anyone elaborate why I should use MediatorLiveData
instead of just having simple check?
kotlin android-room android-livedata kotlin-extension
kotlin android-room android-livedata kotlin-extension
asked Nov 15 at 1:58
musooff
15711
15711
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311354%2fmediatorlivedata-vs-livedata%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown