Fixed
Status Update
Comments
ra...@gmail.com <ra...@gmail.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #3
yea i'll take it.
jb...@google.com <jb...@google.com> #4
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
Component used: lifecycle-livedata-ktx
Version used: 2.4.0
Devices/Android versions reproduced on: n/a
When refactoring, it's easy to accidentally end up with
when you intended
it's quite difficult to spot the difference, and the compiler gives no warning here, even though there's no use in calling map/switchMap without using the result.
Can you add @CheckResult to the LiveData.switchMap/map/distinctUntilChanged extension functions?