Releases: raamcosta/compose-destinations
Releases · raamcosta/compose-destinations
1.10.0
1.9.63
1.9.62
1.9.61
[regression found use 1.9.59 until fix] 1.9.60
1.9.59
1.9.58
Changes
- Fixed #524
- Fixed an issue where ResultRecipients were not considering the correct Destination as sender when validating types, in some specific scenarios
Full Changelog: 1.9.57...1.9.58
1.9.57
What changed
- Fixes #541
- We now allow a parameter on the annotated Composable of the same type of the
navArgsDelegateeven if (and this is the new bit) that type is also a navigation argument type.
So, this:
@Serializable
data class SomeSerializable(...)
@Destination(
navArgsDelegate = SomeSerializable:class
)
@Composable
fun SomeScreen(
navArgs: SomeSerializable
)Will now work, and navArgs parameter will be provided by the library.
Before, since navArgs is Serializable, Compose Destinations would treat it as a new nav argument, but since you were specifying a delegate to define the nav args, it didn't allow you to do that.
NOTE that the navArgsDelegate class doesn't need to be Serializable itself, each field will corresponde to one nav argument, so only the fields need to be considered a nav argument type. (list is on https://composedestinations.rafaelcosta.xyz/destination-arguments/navigation-arguments#basics).
Full Changelog: 1.9.56...1.9.57
