Status Update
Comments
le...@google.com <le...@google.com>
ch...@google.com <ch...@google.com>
ch...@google.com <ch...@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.
al...@google.com <al...@google.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-
Description
lmao
Tested on compose versions 1.1.1 and 1.3.0-rc01
Basically:
OpenClass
flow
PeskyFun
Also, it will not work if it's inside of specific lambda functions of specific composables, for example:Row { flow.collectAsState().value }
will trigger this, butButton(onClick = {...}) { flow.collectAsState().value }
will not.ChildClass
Example: