Fixed
Status Update
Comments
jb...@google.com <jb...@google.com> #2
Could we get an official response to this feature request? Is there an idea to support SafeArgs in navigation-compose one day? Not asking for any time frames. Maybe there is no plans for statically generated args for navigation-compose at all.
zh...@gmail.com <zh...@gmail.com> #3
Please check out my implementation of the same-
Part 1-https://proandroiddev.com/safe-compose-arguments-an-improved-way-to-navigate-in-jetpack-compose-95c84722eec2
Part 2-https://proandroiddev.com/safe-compose-arguments-an-improved-way-to-navigate-in-jetpack-compose-part-2-218a6ae7a027
Github repo-https://github.com/dilrajsingh1997/safe-compose-args
Part 1-
Part 2-
Github repo-
jb...@google.com <jb...@google.com>
cl...@google.com <cl...@google.com> #5
+1
zh...@gmail.com <zh...@gmail.com> #6
this library make it super easy if can you support this on the native way
cl...@google.com <cl...@google.com> #7
Here's a library that does just this:
cl...@google.com <cl...@google.com> #8
+1
something similar to 'compose-destinations' should be officially available to the devs. Its a pain to manage all the parameters manually.
Currently, I am working with a custom NavType implementation with Gson.
something similar to 'compose-destinations' should be officially available to the devs. Its a pain to manage all the parameters manually.
Currently, I am working with a custom NavType implementation with Gson.
ap...@google.com <ap...@google.com> #9
The current navigation is really difficult to use. It makes me unwilling to use composite in new projects and upgrade in outdated projects
pr...@google.com <pr...@google.com> #10
Google team are there any news/priorities on this? Are you planning on improve the existing compose-navigation lib or this is going to not feasible😉?
Description
Component used: Navigation Version used: Devices/Android versions reproduced on:
If this is a bug in the library, we would appreciate if you could attach:
When the user clicks the button twice in a row, the button event is a pop-up window, and then two pop-up windows will appear
The interesting thing is that when I close the pop-up window at the top of the stack, the two pop-up windows will be added to
NavigatorState#_transitionsInProgress
, and then the pop-up window at the top of the stack will be destroyed from compose and executedialogNavigator#onTransitionComplete
, but the second pop-up If the window does not executedialogNavigator#onTransitionComplete
, the second lifeCycle will always be in the START state, which will cause NavController data exceptionI compared
screen
andDialogHost
in the composable function ofNavHost
, and found that Screen will executeonTransitionComplete
after the state changes, while Dialog does not