Fixed
Status Update
No update yet.
Comments
il...@google.com
il...@google.com
ap...@google.com
Is this specific to navigation? Or can this be reproduced with another other Composable component?
il...@google.com
It only happens inside of a NavHost. So, yes, it seems to be specific to navigation.
Description
Currently, the `Navigation` class has 2 signatures for `createNavigateOnClickListener`:
`createNavigateOnClickListener(final int resId)`
`createNavigateOnClickListener(final int resId, finalBundle args)`
I propose a third overload:
`createNavigateOnClickListener(NavDirections)`
This overload could trampoline to the other two, as necessary, but it would allow for users to avoid having to manually extract the ActionID and Bundle from the NavDirections. It would be a nicety on top of an already nice library :)