Releases: raamcosta/compose-destinations
2.0.0-beta10
Changes
- Result back feature now supports all types that normal navigation supports! 🚀
- New debug mode
- Small improvements
Result back feature now supports all types that normal navigation supports! 🚀
Previously, only these result types were allowed:
- String, Boolean, Float, Int, Long, Serializable, or Parcelable.
- Type cannot have type arguments itself (f.e you can't use Array even though it is Serializable)
Now it allows all of these (same as normal navigation):
- String
- Boolean
- Int
- Long
- Float
- Parcelable
- Serializable
- Enums
- @kotlinx.serialization.Serializable annotated types
- Custom navigation types (Types for which the user has defined a serialization to and from string)
- Array and ArrayList of the above types
For Boolean, Int, Float, Long, you'll need to use BooleanArray, IntArray, FloatArray, LongArray instead of Array, Array, Array, Array.
ResultBackNavigator
or a ResultRecipient
you will need to update those calls to pass in a DestinationsNavType
corresponding to your result type.
You can check the corresponding generated Destination and see how it calls your Composable, and do the same, or you can just start typing your result class type name (lower case) and IDE will help you.
For example, if your Destination receives a:
ResultBackNavigator<Boolean>
you'll want to pass inresultBackNavigator(booleanNavType)
(booleanNavType
is a top level field you can import from core library)ResultBackNavigator<MyParcelableClass>
you'll passresultBackNavigator(myParcelableClassNavType)
(myParcelableClassNavType
is a top level field you can import from generated code).
If not calling it manually, then generated code will do this for you, so no need to change anything in that case.
New debug mode
This is mainly to help me understand users' setup when there's a reported issue so that I can find the root cause and fix it quicker.
New ksp configuration added:
ksp {
arg("compose-destinations.debugMode", "$rootDir")
}
When set, it will write some debug files to a folder on $rootDir/composeDestinationsDebug
(taking above example).
Please make sure to:
- add this configuration for all modules that use compose destinations ksp
- do ./gradle clean and delete previous debug folder
- run the app or build the project
- share the files with me somehow (ex: through the github issue, DM on Kotlin slack, etc).
- remove the configuration and delete the debug folder
DO NOT leave the configuration ON as it may slow down builds for no reason, just remove it after sending me the files.
Full Changelog: 2.0.0-beta09...2.0.0-beta10
1.11.5-beta
2.1.0-beta09
Changes
- Fixes #648
- Fixes issue with module name being prefixed on the NavGraphs module object fields.
Full Changelog: 2.1.0-beta08...2.1.0-beta09
2.0.0-beta09
Changes
- Fixes #648
- Fixes issue with module name being prefixed on the NavGraphs module object fields.
Full Changelog: 2.0.0-beta08...2.0.0-beta09
2.1.0-beta08
Changes
- Fixes #638 by @extmkv in #641
- Module names will now prefix all routes when set
- Should help avoid duplicate routes on bigger projects
Full Changelog: 2.1.0-beta07...2.1.0-beta08
2.0.0-beta08
Changes
- Fixes #638
- Module names will now prefix all routes when set
- Should help avoid duplicate routes on bigger projects
Full Changelog: 2.0.0-beta07...2.0.0-beta08
2.1.0-beta07
Changes
- Fixes #638 by @extmkv in #640
- Fixes #611
- Improved wrong nav graph args configuration reporting
- When generating docs to specific directories set with gradle ksp configs, it creates missing directories if any.
- Added API for adding deep links at runtime (Fixes #639)
Example:
DestinationsNavHost(
//...
) {
MyDestination addDeepLink { uriPattern = "schema://${MyDestination.route}" }
}
Full Changelog: 2.1.0-beta06...2.1.0-beta07
2.0.0-beta07
Changes
- Fixes #638
- Fixes #611
- Improved wrong nav graph args configuration reporting
- When generating docs to specific directories set with gradle ksp configs, it creates missing directories if any.
- Added API for adding deep links at runtime (Fixes #639)
Example:
DestinationsNavHost(
//...
) {
MyDestination addDeepLink { uriPattern = "schema://${MyDestination.route}" }
}
Full Changelog: 2.1.0-beta06...2.0.0-beta07
2.1.0-beta06
Changes
Full Changelog: 2.0.0-beta05...2.0.0-beta06