Status Update
Comments
es...@gmail.com <es...@gmail.com> #2
es...@gmail.com <es...@gmail.com> #3
since it is already marked as deprecated, we can probably do it by now.
es...@gmail.com <es...@gmail.com> #4
es...@gmail.com <es...@gmail.com> #5
Branch: androidx-master-dev
commit d576cbdc911cba16638a44fd8223391a90a07ef7
Author: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>
Date: Tue Aug 11 09:30:34 2020
[GH] Hide deprecated internal API.
## Proposed Changes
* `RoomDatabase.java` has protected `mCallbacks` field which is leaking in the API docs, we should @Hide it.
## Testing
Test: Ran unit tests locally
## Issues Fixed
Fixes: 76109329
This is an imported pull request from
Resolves #61
Github-Pr-Head-Sha: 6440daa3a63752c7f9d5ba2a390248cd85bc634f
GitOrigin-RevId: fe92d8466a59b44b218b6ca3cbd57dcda17992f7
Change-Id: Id599cdf5b02b32bdae0166266fb7da967598fe92
A room/runtime/api/current.ignore
M room/runtime/api/current.txt
M room/runtime/api/public_plus_experimental_current.txt
M room/runtime/api/restricted_current.txt
M room/runtime/src/main/java/androidx/room/RoomDatabase.java
ap...@google.com <ap...@google.com> #6
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Add non-reified overloads for toRoute
Expand for full commit details
Add non-reified overloads for toRoute
NavBackStackEntry.toRoute and SavedStateHandle.toRoute overloads that take a KClass<*> as route and returns T.
Test: existing tests pass
Bug: 366291612
Relnote: "Added non-reified overload for NavBackStackEntry.toRoute and SavedStateHandle.toRoute that takes in a KClass<*> as route"
Change-Id: Ic1bf09bdd59e0d96db7edb89276ac31a977d6602
Files:
- M
navigation/navigation-common/api/current.txt
- M
navigation/navigation-common/api/restricted_current.txt
- M
navigation/navigation-common/src/main/java/androidx/navigation/NavBackStackEntry.kt
- M
navigation/navigation-common/src/main/java/androidx/navigation/SavedStateHandle.kt
Hash: 2c4a084bdbe543ded4b6d203c6636fc825e7e301
Date: Wed Nov 06 16:22:20 2024
cl...@google.com <cl...@google.com>
es...@gmail.com <es...@gmail.com> #7
I think its also better to add non-reified dialog
. I might have a use case for it soon.
ap...@google.com <ap...@google.com> #8
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Add non-reified overload for composable and navigation
Expand for full commit details
Add non-reified overload for composable and navigation
Overloads that take a KClass<*> as the route for composable destination and nested graph
Test: existing tests
Bug: 366291612
Relnote: "Added overloads for NavGraphBuilder.composable and NavGraphBuilder.navigation that takes a KClass<*> as the route."
Change-Id: If56a553a4d2608a5eb059ea684e566a4feae955b
Files:
- M
navigation/navigation-compose/api/current.txt
- M
navigation/navigation-compose/api/restricted_current.txt
- M
navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavGraphBuilder.kt
Hash: 9cd16b12e255b5e7ad3c8cc7fca08dc63faf9e52
Date: Wed Nov 27 14:08:15 2024
cl...@google.com <cl...@google.com> #9
Fixed internally and available in navigation-2.9.0-alpha04
ap...@google.com <ap...@google.com> #10
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Add non-reified NavGraphBuilder.dialog safe args api
Expand for full commit details
Add non-reified NavGraphBuilder.dialog safe args api
Test: ./gradlew navigation:navigation-compose:cC
Bug: 366291612
Relnote: "Added non-reified NavGraphBuilder.dialog API to create a composable dialog with KClass<T>"
Change-Id: Iba4ee26b906c09e7ec47b7e940cf689788c117e8
Files:
- M
navigation/navigation-compose/api/current.txt
- M
navigation/navigation-compose/api/restricted_current.txt
- M
navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavGraphBuilderTest.kt
- M
navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavGraphBuilder.kt
Hash: f96150f5be412aa3d660efd83ba07d439e1da211
Date: Wed Dec 04 13:51:14 2024
ap...@google.com <ap...@google.com> #11
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Update non-reified composable and navigation
Expand for full commit details
Update non-reified composable and navigation
Added <T : Any> type parameter to the API
Test: ./gradlew navigation:navigation-compose:cC
Bug: 366291612
Relnote: "Non-reified composable and navigation API expects route from KClass<T> instead of KClass<*>"
Change-Id: Icd47da4061103edd8462a729ae168e724d833d36
Files:
- M
navigation/navigation-compose/api/current.txt
- M
navigation/navigation-compose/api/restricted_current.txt
- M
navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavGraphBuilderTest.kt
- M
navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavGraphBuilder.kt
Hash: 653f2ea988ff3744ecf3de08c3221c4ee8c64917
Date: Wed Dec 04 13:41:46 2024
pr...@google.com <pr...@google.com> #12
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.navigation:navigation-common:2.9.0-alpha04
androidx.navigation:navigation-compose:2.9.0-alpha04
Description
Component used: Navigation Version used: 2.8.0
I'm currently using Voyager but decided to try migrating to Compose Navigation as it already provides better type-safety. However, I find it difficult to migrate since the Api is lacking in some way while there are some that are available but is only limited to the Library Scope.
This is in conjunction with Issue 361863272
I would like to request non-reified
navigation
,composable
, andNavBackStackEntry.toRoute()
wherein you can enter the class's KClass as a parameter.Voyager provides
Screen
, andTab
interfaces which could easily be implemented and extended to another interface or abstract class wherein you could create a common Class with common implementations you can tailor according to your needs. Compose Navigation currently doesn't support this but it is much more scalable especially with deeplinks.Migration to Compose Navigation without any interface proves to be difficult unless the above requested are given. I have here an example implementation of interfaces. I don't know how much effective it will be but technically it could be applied to my project to some extent since there are a lot of caveats I don't know of. It would be much better if Compose Team can provide similar interfaces which could greatly boost migration to the library.