Fixed
Status Update
No update yet.
Comments
ap...@google.com
We have got to get a better way to handle deprecations. This is awful.
jb...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 387ce59c6290b334c790f270d98f1b1dde5d3391
Author: Alan Viverette <alanv@google.com>
Date: Wed Nov 29 11:26:23 2023
Clean up obsolete compat methods in ViewCompat and usages in core
Doesn't update lint baseline yet because there are lots of unrelated
changes there. We'll handle the baseline after we clean up the rest of
core.
Doesn't update usages outside of core or core-ktx. These should be
handled by individual library owners.
Bug: 313834577
Test: ViewCompatTest
Relnote: Deprecated obsolete compat methods in ViewCompat
Change-Id: I0bfc2cd15dc681ba0c09f795d25622f2ade004d6
M core/core-ktx/src/main/java/androidx/core/view/View.kt
M core/core/api/current.txt
M core/core/api/restricted_current.txt
M core/core/src/main/java/androidx/core/view/ViewCompat.java
M development/build_log_simplifier/messages.ignore
https://android-review.googlesource.com/2852865
Branch: androidx-main
commit 387ce59c6290b334c790f270d98f1b1dde5d3391
Author: Alan Viverette <alanv@google.com>
Date: Wed Nov 29 11:26:23 2023
Clean up obsolete compat methods in ViewCompat and usages in core
Doesn't update lint baseline yet because there are lots of unrelated
changes there. We'll handle the baseline after we clean up the rest of
core.
Doesn't update usages outside of core or core-ktx. These should be
handled by individual library owners.
Bug: 313834577
Test: ViewCompatTest
Relnote: Deprecated obsolete compat methods in ViewCompat
Change-Id: I0bfc2cd15dc681ba0c09f795d25622f2ade004d6
M core/core-ktx/src/main/java/androidx/core/view/View.kt
M core/core/api/current.txt
M core/core/api/restricted_current.txt
M core/core/src/main/java/androidx/core/view/ViewCompat.java
M development/build_log_simplifier/messages.ignore
Description
When adding the stateless
SavedStateViewModelFactoryconstructor inAndroidViewModelFactoryunder the hood, which meant that when using the statelessSavedStateViewModelFactoryand creating aViewModelviaCreationExtras, it required anApplicationto be set.Having an
Applicationshould not be a requirement for creating aViewModelusing theSavedStateViewModelFactoryor theAndroidViewModelFactory. We should fix the behavior of theAndroidViewModelFactoryto rely on theNewInstanceFactorywhen no application is available, just like theSavedStateViewModelFactoryused to.