Fixed
Status Update
Comments
hu...@gmail.com <hu...@gmail.com> #2
I also have the same issue so it seems to be a real problem.
tn...@google.com <tn...@google.com>
tn...@google.com <tn...@google.com> #4
why is this marked has Obsolete? this is still a bug that is happening and its difficult to fix.
for all who are looking for a solution use this:
http://stackoverflow.com/questions/16200972/android-css-positionfixed-after-a-device-rotate
for all who are looking for a solution use this:
tn...@google.com <tn...@google.com> #5
I've tweaked the typealias test mode to skip the following types:
- @Composable () -> Unit
- @Composable (() -> Unit)?
- @Composable () -> Unit)?
tn...@google.com <tn...@google.com> #6
These are excluded via
But just as is done for compose (and as indicated by the test mode when it fails the test), you can deliberately skip this test mode from your lint check if you don't think your detector needs to handle type aliases.
Description
Thant's because when we have class like:
public class SomeNamedClass {
public void someMethod() {
ArgumentLiveData<Object, Object> anonymous = ArgumentLiveData.create(new Function<Object, LiveData<Object>>() {
@Override
public LiveData<Object> apply(Object input) {
return null;
}
});
}
}
in TestMode.TYPE_ALIAS, it's look like:
class SomeNamedClass {
fun someMethod() {
val anonymous = ArgumentLiveData.create(object : Function<Any, LiveData<Any>> {
override fun apply(input: Any?): LiveData<Any> {
return MutableLiveData()
}
})
}
}
which cause exception when analyze it.