Now that we have the official `kotlin.uuid.Uuid` serialization support coming in Kotlin 2.1.0, is th...

# compose

[Armond Avanes]

Now that we have the official kotlin.uuid.Uuid serialization support coming in Kotlin 2.1.0, is there any plan to support Uuid as a built-in type in Navigation Compose safe arguments?
Currently we have to add a custom NavType to any navigation composable which is going to accept kotlin.uuid.Uuid as a safe argument.

[Hristijan]

Currently we have to add a custom NavType to any navigation composable which is going to accept kotlin.uuid.Uuid as a safe argument.

Doing the same or passing a string at the moment but only at a place where the string part of the Uuid is used.

[Ian Lake]

You can file an issue: https://issuetracker.google.com/issues/new?component=409828&template=1093757

Just keep in mind that it will be a while before Navigation depends on Kotlin 2.1.0

[Armond Avanes]

Thanks for your response Ian. I just filed this ticket: https://issuetracker.google.com/issues/371237540

[Stylianos Gakis]

Providing a custom NavType for the UUID should also be trivial to do in your own code

[Armond Avanes]

@Stylianos Gakis I'm already using custom NavType, but repeating the same for every single composable, accepting Uuid as safe argument, is not optimal. That was my point and having a built-in support will resolve this issue.

[Stylianos Gakis]

Filing an issue sounds like your best bet then