Assigned
Status Update
Comments
mm...@commonsware.com <mm...@commonsware.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.
vi...@google.com <vi...@google.com>
mm...@commonsware.com <mm...@commonsware.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
Studio Build:
4.0.0
6.1.1
Steps to Reproduce:
MainActivity
and notice that thegenerateWithoutContext()
function has no inspection warningsMainActivity
and itsgenerateWithContext()
functionExpected Results: no inspection warnings, as the two functions are equivalent, except that
generateWithContext()
uses a customCoroutineContext
along withDispatchers.IO
Actual Result: "Inappropriate blocking method call" inspection warning
Basically, this inspection does not appear to be able to handle
+
chains of coroutine contexts.Thanks for considering this!