Fixed
Status Update
No update yet.
Comments
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 20112348e9cf68cf81ae9b54fb3c0b18150edb71
Author: Marcello Galhardo <mgalhardo@google.com>
Date: Fri May 10 11:10:17 2024
Move `compose-ui` to `androidMain` in `viewmodel-compose`
Test: N/A
Fixes: 339562627
Change-Id: Ia3b0638b3f4b61ba760d3c10337275a255d898e8
M lifecycle/lifecycle-viewmodel-compose/build.gradle
https://android-review.googlesource.com/3079334
Branch: androidx-main
commit 20112348e9cf68cf81ae9b54fb3c0b18150edb71
Author: Marcello Galhardo <mgalhardo@google.com>
Date: Fri May 10 11:10:17 2024
Move `compose-ui` to `androidMain` in `viewmodel-compose`
Test: N/A
Fixes: 339562627
Change-Id: Ia3b0638b3f4b61ba760d3c10337275a255d898e8
M lifecycle/lifecycle-viewmodel-compose/build.gradle
Description
Version used: 1.0.0-alpha06
Navigation has the ability to set a default graph from your manifest via NavController.setMetadataGraph() and NavInflater.inflateMetadataGraph().
The existence of this API promotes bad patterns (automatic defaults that reside far from the code invoking it) and can outright break other functionality such as setting a programmatically inflated NavGraph onto a NavHostFragment (as NavHostFragment will use the metadata graph by default, calling setGraph with the wrong graph).
These API should be removed entirely to prevent issues - developers should call NavHostFragment.create() or call setGraph() with exactly the graph they want.