Fixed
Status Update
Comments
se...@google.com <se...@google.com>
se...@google.com <se...@google.com>
da...@google.com <da...@google.com>
il...@google.com <il...@google.com> #2
You should just continue to use startActivityForResult+override onActivityResult in your Fragment - this wouldn't be part of your navigation graph.
I'd like to know more about what integration you were expecting and what you'd like to see.
I'd like to know more about what integration you were expecting and what you'd like to see.
Description
Version used: 1.0.0-alpha01
Devices/Android versions reproduced on: -
The generated NavDirections classes currently do not have an equals/hashcode method or public access to the individual arguments making them hard to be used in unit tests (e.g. is the correct direction with the right arguments created).
The generated Args classes have a Builder making it easy to create without a bundle for tests, but a small enhancement would be having an empty Builder to set the invidual arguments using the setter methods available.