Status Update
Comments
an...@backx.org <an...@backx.org> #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.
il...@google.com <il...@google.com> #3
Part 1-
Part 2-
Github repo-
an...@backx.org <an...@backx.org> #6
this library make it super easy if can you support this on the native way
be...@google.com <be...@google.com> #7
Here's a library that does just this:
il...@google.com <il...@google.com> #8
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.
il...@google.com <il...@google.com> #9
an...@backx.org <an...@backx.org> #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😉?
ra...@gmail.com <ra...@gmail.com> #12
Re navigate
calls) from @Serializable
classes.
There's a lot of parts to this, so please bear with us. We'll make sure to write a public blog post explaining much of the reasoning and other alternatives we looked into when we're ready to make a public release.
Description
Version used: 1.0.0-alpha02
Devices/Android versions reproduced on: Nexus 5, OnePlus One
We want to implement nested NavHostFragments because we want to navigate between 2 screens that each have 2 different Bottom Navigation Bars. We also thought about nesting NavHostFragments so we can bind ViewModels to a navigation part of our app. Parts that need to clean up the data they were using after being navigated through. The problem we're facing is that the outer most NavHostFragment intercepts the back button navigation before the child NavHostFragments do. The result is that when pressing the back button, it completely goes back to the destination before the child NavHostFragment. Are there any plans to support nesting NavHostFragments or is there a different solution to nested navigation that is seemingly not supported by nesting navigation graphs because I don't see how you can for example navigate between fragments with different Bottom Navigation Bars and navigate the fragments that belong to the Bottom Navigation Bar?