Fixed
Status Update
Comments
ra...@gmail.com <ra...@gmail.com> #2
The only currently supported strategy for adding Fragments to compose is via
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #3
Yes, I am familiar with AndroidViewBinding, however, as far as I know it has some limitations, like, I can't decide at runtime what fragment to commit.
jb...@google.com <jb...@google.com> #4
I also can't give parameters to the fragment being inflated.
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?