Fixed
Status Update
Comments
jb...@google.com <jb...@google.com>
th...@gmail.com <th...@gmail.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.
al...@gmail.com <al...@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-
ma...@sainsburysbank.co.uk <ma...@sainsburysbank.co.uk> #5
+1
ap...@google.com <ap...@google.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:
ma...@sainsburysbank.co.uk <ma...@sainsburysbank.co.uk> #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.
na...@google.com <na...@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
cn...@gmail.com <cn...@gmail.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
Version used: 2.6
Devices/Android versions reproduced on: All
When using Navigation 2.6.0 There is an issue when poping backstack twice rapidely, for example if you have 3 fragments A, B, C with navigation from A to B and B to C, if you try to pop backstack quickly twice from fragment C you ending up to fragment A as expected but you current desination is fragment B instead of fragment A.
2.5.x is working without this issue.
Checked attched example