Fixed
Status Update
No update yet.
Comments
js...@google.com
js...@google.com
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.
js...@google.com
go...@jakewharton.com
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-
[Deleted User] <[Deleted User]>
+1
mk...@google.com
this library make it super easy if can you support this on the native way
ap...@google.com
Here's a library that does just this:
ap...@google.com
+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
The current navigation is really difficult to use. It makes me unwilling to use composite in new projects and upgrade in outdated projects
mk...@google.com
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
* checkParameterIsNotNull --> checkNotNullParameter:
* checkExpressionValueIsNotNull --> checkNotNullExpressionValue:
* throwNpe --> checkNotNull:
It would be nice to have these honored before 1.4 comes out (months away) and regresses null handling.
Associated Kotlin bug: