Component used: Navigation
Version used: 2.1.0 alpha 05

Deep links with arguments that are enum types are not recognized and parsed unless the casing in the deeplink is an exact match to the enum. This may not be feasible to fix/add, but wanted to bring it up just in case.

consider an example where I have an enum like so

enum class Colors {
RED,
BLUE,
GREEN
}

And a destination with an argument that takes a Colors, and supports a deeplink

<argument
android:name="destColor"
app:argType="com.my.app.Colors"
android:defaultValue="RED" />
<deepLink
app:uri="https://myapp.com/{destColor}" />

The deeplink will only work if the color is correctly cased:
https://myapp.com/RED
https://myapp.com/BLUE
https://myapp.com/GREEN

And the following will NOT work:

https://myapp.com/red
https://myapp.com/blue
https://myapp.com/green

Granted, paths in URI's are by rule considered to be case-sensitive, so https://myapp.com/RED and https://myapp.com/red could potentially point to 2 different resources. However, a great many users of the web (namely, anyone using IIS, which treats URI's as case-INsensitive) consider uri's to be case insensitive.

It would be nice if perhaps when setting up a destination argument of an enum type (or maybe when defining a deep link) we had the option to specify that a deeplink should or should not match based on case-sensitivity. Of course, there's still the challenge of parsing "red" to Colors.RED when processing the deep link arguments.

Issue 135857840

Mentioned issues (1)

Links (15)

Issue metadata