Fixed
Status Update
Comments
se...@google.com <se...@google.com>
wk...@google.com <wk...@google.com>
il...@google.com <il...@google.com> #2
As of the upcoming alpha03, String and Parcelable arguments (added in https://issuetracker.google.com/issues/79563966 ) will be able to use the app:nullable="true" attribute to declare that they support null values in Safe Args (by default, they will be non-null).
th...@gmail.com <th...@gmail.com> #3
Could you add support for "@null" as default value as well? Currently when using app:nullable="true" in combination with android:defaultValue="@null", the generated file will have the default value "@null" as string value instead of null value.
wk...@google.com <wk...@google.com> #4
That's probably a bug if that's the case.
I've created b/111425916 to track this
I've created
Description
Version used: 1.0.0-alpha-01
Devices/Android versions reproduced on: -
Safe args are a great enhancement for navigation. A great addition to that would be being able to define nullability for arguments. An example for how this would look like:
<argument android:name="id" app:type="string?"/>
(note the ? for the type) - an alternative would be to have another attribute - e.g. app:required="false" to make it less tied to Kotlin. The generated Args and NavDirections class would have the Nullable/NonNull annotations.
This would make it very obvious which arguments are required and which are optional - especially in Kotlin.