Status Update
No update yet.
Comments
sz...@gmail.com
cs...@gmail.com
Feel free to do so and we will review.
na...@vitruvian.me
I think your PR also fixes our problem: we have links like
.../search/
.../search?documentId=123
.../search?folder=123
And each should be redirected to different navigation destinations. Currently they all redirect to one page, and sometimes crash.
cs...@twoupdigital.com
Thank you for the PR!
This has been fixed internally and will be available as part of the Navigation 2.4.0-alpha08 release.
da...@gmail.com
Just a quick note. It seems like NavInflater don't set defaultValue when using android:defaultValue="@null" and thus the check will fail. You will have to add the query argument in your Uri : "
jb...@google.com
ap...@google.com
I filed an issue RE: #8 ... an @null default value should not be flagged as "required", and should not fail and cause the app to crash.
jb...@google.com
This has been fixed internally and will be available in the Navigation 2.8.0-alpha04 release.
na...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.navigation:navigation-compose:2.8.0-alpha04
Description
How exactly we want to take that variable, is not yet clear, but it could be something read at the destination level as part of the enter destination's transition.