Fixed
Status Update
Comments
il...@google.com <il...@google.com>
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
Any update on this?
The request is DiffUtil implementation along with "items" and "indexedItems" functions to support DiffUtil and animations when adding/removing items. the same as the ListAdapter with DiffUtil.
The request is DiffUtil implementation along with "items" and "indexedItems" functions to support DiffUtil and animations when adding/removing items. the same as the ListAdapter with DiffUtil.
il...@google.com <il...@google.com> #3
We are working on it, but nothing to share yet. Thanks
Description
For example, if I had an action defined similarly to the following example:
```
fragment<MyFragment>("my_fragment_dest_id") {
...
argument("my_arg") {
type = NavType.StringType
}
}
```
I would expect to be able to create an action to that destination that provides a default argument, like the following (or something similar).
```
action("my_action_id") {
destinationId = "my_fragment_dest_id"
argument("my_arg") {
defaultValue = "action_provided_default_value"
}
}
}
```
This seems like something that would be important to keep in parity with the functionality provided by the XML navigation graph resource.