Fixed
Status Update
Comments
m6...@mschmitt.info <m6...@mschmitt.info> #2
Status is still Assigned, but Compose 1.1.0 was already released. Did the ETA change for this feature?
yb...@google.com <yb...@google.com> #3
The Compose Animation APIs Navigation needs (such as AnimatedContent
) are still @Experimental
in Compose 1.1.0.
to...@gmail.com <to...@gmail.com> #4
Update: Same case for Compose 1.2.0
yb...@google.com <yb...@google.com>
yb...@google.com <yb...@google.com> #5
why is this taking so long?
Description
Version used: 1.0.0-alpha2
Devices/Android versions reproduced on: N/A
If my entities subclass BaseObservable then they gain an `mCallbacks` field of type `PropertyChangeRegistry` that Room doesn't know how to handle, because of the `private transient PropertyChangeRegistry mCallbacks` on BaseObservable.
I can bodge this be defining a stub TypeConverter and adding a dummy getter/setter, but that's pretty nasty.
I feel that transient fields should be treated as if they were annotated as @Ignore.