IssueTracker

Component used: Navigation Version used: 2.3.5

It is often convenient to specify default argument values in an action, for example when multiple actions point to the same destination.

Sometimes we only specify values for some arguments:

<fragment
    android:id="@+id/firstFragment"
    android:name="package.FirstFragment">
    <action
        android:id="@+id/goToSecond"
        app:destination="@id/secondFragment">
        <argument
            android:name="argTwo"
            android:defaultValue="42" />
    </action>
</fragment>
<fragment
    android:id="@+id/secondFragment"
    android:name="package.SecondFragment">
    <argument
        android:name="argOne"
        app:argType="string" />
    <argument
        android:name="argTwo"
        app:argType="integer" />
</fragment>

We then would like to call it like this: FirstFragmentDirections.goToSecond("one!").

But unfortunately, SafeArgs generates code with parameters in the wrong order: argTwo (with default value), then argOne. See attached project.

I suppose better options would be to:

1. Respect arguments order from the destination (seems more intuitive), or
2. Always place default parameters last (looks nicer in Kotlin).