Standalone Sealed Classes as NavArgs in Android about compose-destinations HOT 5 OPEN

When setting the navArgs in the destination annotation, the class is not the navigation argument, it’s just a class where navigation arguments are defined. So it doesn’t make sense for such a class to be a sealed type: you need a predefined set of arguments, you can’t tell the official nav lib “my arguments can either be these or these other”.

Im on the phone sorry for not formatting the reply, hopefully it’s understandable.

I’ve seen this confusion lately. Maybe I’ll enforce these classes to be named always SomehtingNavArgs to make it clear the args are its fields not itself.

from compose-destinations.

Another thing: the class passed to Destination annotation navArgs does not need to be itself Parcelable or any other valid navigation type, precisely because it will not be serialised. Instead its fields will.

from compose-destinations.