Update composeDestinations to v2.2.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.github.raamcosta.compose-destinations:ksp	2.1.0-beta11 -> 2.2.0
io.github.raamcosta.compose-destinations:core	2.1.0-beta11 -> 2.2.0

---

Release Notes

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

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 https://github.com/raamcosta/compose-destinations/pull/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 https://github.com/raamcosta/compose-destinations/pull/643

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

v2.1.0-beta16

Compare Source

Changes

• Dependency updates

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

v2.1.0-beta15

Compare Source

What's Changed

• Dependency updates by @​Rawa in https://github.com/raamcosta/compose-destinations/pull/708

New Contributors

• @​Rawa made their first contribution in https://github.com/raamcosta/compose-destinations/pull/708

Full Changelog: raamcosta/compose-destinations@2.1.0-beta14...2.1.0-beta15

v2.1.0-beta14

Compare Source

Changes

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

Full Changelog: raamcosta/compose-destinations@2.1.0-beta13...2.1.0-beta14

v2.1.0-beta13

Compare Source

v2.1.0-beta12

Compare Source

Changes

• Update dependencies to Compose 1.7 and Compose Navigation 2.8 by @​extmkv in https://github.com/raamcosta/compose-destinations/pull/680

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

---

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.