Update compose.destinations to v2.0.0-beta12

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.github.raamcosta.compose-destinations:ksp	2.0.0-beta01 -> 2.0.0-beta12
io.github.raamcosta.compose-destinations:core	2.0.0-beta01 -> 2.0.0-beta12

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

raamcosta/compose-destinations (io.github.raamcosta.compose-destinations:ksp)

v2.0.0-beta12

Compare Source

Changes

• Fixes #​678
• Improve error message when using ResultBackNavigator with unsupported type.

Full Changelog: raamcosta/compose-destinations@2.0.0-beta11...2.0.0-beta12

v2.0.0-beta11

Compare Source

Changes

• Fixes #​668
• Check release notes of previous release if you're coming from beta09 or below

Full Changelog: raamcosta/compose-destinations@2.0.0-beta10...2.0.0-beta11

v2.0.0-beta10

Compare Source

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.

⚠️ If you were manually calling a Composable Destination which receives either a 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 in resultBackNavigator(booleanNavType) (booleanNavType is a top level field you can import from core library)
• ResultBackNavigator<MyParcelableClass> you'll pass resultBackNavigator(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: raamcosta/compose-destinations@2.0.0-beta09...2.0.0-beta10

v2.0.0-beta09

Compare Source

Changes

• Fixes #​648
• Fixes issue with module name being prefixed on the NavGraphs module object fields.

Full Changelog: raamcosta/compose-destinations@2.0.0-beta08...2.0.0-beta09

v2.0.0-beta08

Compare Source

Changes

• Fixes #​638
• Module names will now prefix all routes when set
  • Should help avoid duplicate routes on bigger projects

Full Changelog: raamcosta/compose-destinations@2.0.0-beta07...2.0.0-beta08

v2.0.0-beta07

Compare Source

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: raamcosta/compose-destinations@2.1.0-beta06...2.0.0-beta07

v2.0.0-beta06

Compare Source

Changes

• Fixes #​624
• Fixes #​638
• Fixes #​636

Full Changelog: raamcosta/compose-destinations@2.0.0-beta05...2.0.0-beta06

v2.0.0-beta05

Compare Source

v2.0.0-beta04

Compare Source

v2.0.0-beta02

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.