Update composeDestinations to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
io.github.raamcosta.compose-destinations:ksp	1.9.57 -> 2.3.0
io.github.raamcosta.compose-destinations:core	1.9.57 -> 2.3.0

---

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.3.0

Compare Source

Main changes

• Updated Compose to 1.9, compose jetpack navigation and Kotlin.

Full Changelog: raamcosta/compose-destinations@2.2.0...2.3.0

v2.2.0

Compare Source

What changed

• Fixes issues related to KSP v2
• Fixes #​736
• Fixes #​728
• Fixes #​714
• Fixes #​719
• Improve error messages and docs
• Dependency updates

Optional result back in ON_RESUME / ON_START #​719

By default, compose destinations will call onNavResult in first opportunity between "onResume" and "onStart". That is because in some situations, I've found that "onResume" is actually not called.
However, that makes it be called mostly in "onStart", and in some other cases it may not be ideal (see #​719).

So, we've introduced a new onNavResult overload that takes a parameter developers can use to choose when they want to receive the result. Example:

@&#8203;Destination<RootGraph>
@&#8203;Composable
fun MyScreen(
    resultRecipient: ResultRecipient<ConfirmationScreenDestination, Boolean>
) {

    resultRecipient.onNavResult(
        deliverResultOn = OpenResultRecipient.DeliverResultOn.RESUME
    ) { result ->
        // ...
    }
}

By default, if you call the overload which does not take any param here, it will use FIRST_OPPORTUNITY to not make a breaking change in behaviour here.

New Destination label (#​714)

Destination annotation now has a new param "label". This is used to set what official navigation library supports in NavDestination.label. Can be useful for monitoring, logging, etc.

@&#8203;Destination<RootGraph>(
    label = "my screen label"
)
@&#8203;Composable
fun MyScreen() {
}

Full Changelog: raamcosta/compose-destinations@2.1.1...2.2.0

v2.1.1

Compare Source

v2.1.0: - First non beta of v2!

Compare Source

What's Changed

• Adapt to KSP2 API changes by @​FooIbar in #​643
• Additional changes to work with KSP2
• Update dependencies

If you're using NavHostDefaultStartArgs annotation

• Make sure to change the top level field with a top level function. There's an issue with resolving type arguments of annotations used in top level fields with KSP2.

New Contributors

• @​FooIbar made their first contribution in #​643

Full Changelog: raamcosta/compose-destinations@2.1.0-beta16...2.1.0

v1.11.9

Compare Source

Changes

• Dependency updates

Full Changelog: raamcosta/compose-destinations@1.11.8...1.11.9

v1.11.8

Compare Source

Changes

• Dependency updates

Full Changelog: raamcosta/compose-destinations@1.11.7...1.11.8

v1.11.7

Compare Source

Changes

• Updated dependencies to latest stable

Full Changelog: raamcosta/compose-destinations@1.11.6...1.11.7

v1.11.6

Compare Source

Changes

• Update dependencies to Compose 1.7 and Compose Navigation 2.8. With this, we depend on stable versions only.

Full Changelog: raamcosta/compose-destinations@1.11.5-beta...1.11.6

v1.10.2

Compare Source

• Fixes #​592

Full Changelog: raamcosta/compose-destinations@1.10.1...1.10.2

v1.10.1

Compare Source

** What changed

• Updated dependencies to latest 1.6 compose stable

Full Changelog: raamcosta/compose-destinations@1.10.0...1.10.1

v1.10.0

Compare Source

Changes

• Update to Compose 1.6
• Fixed an issue with having line comments after nav arguments with certain default values

Full Changelog: raamcosta/compose-destinations@1.9.63...1.10.0

v1.9.63

Compare Source

Changes

• Fixed an issue with having line comments after nav arguments with certain default values

Full Changelog: raamcosta/compose-destinations@1.9.62...1.9.63

v1.9.62

Compare Source

Changes

• Another fix related to default value parsing

Full Changelog: raamcosta/compose-destinations@1.9.61...1.9.62

v1.9.61

Compare Source

Changes

• Fixed regression caused by 1.9.60 changes

Full Changelog: raamcosta/compose-destinations@1.9.60...1.9.61

v1.9.60: [regression found use 1.9.59 until fix] 1.9.60

Compare Source

Changes

• Fixed #​560

Full Changelog: raamcosta/compose-destinations@1.9.59...1.9.60

v1.9.59

Compare Source

Changes

• Fixed #​558

Full Changelog: raamcosta/compose-destinations@1.9.58...1.9.59

v1.9.58

Compare Source

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: raamcosta/compose-destinations@1.9.57...1.9.58

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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.