build(deps): bump the maven-dependencies group with 2 updates

[dependabot]

Bumps the maven-dependencies group with 2 updates: io.github.raamcosta.compose-destinations:core and io.github.raamcosta.compose-destinations:ksp.

Updates io.github.raamcosta.compose-destinations:core from 2.1.0 to 2.3.0

Release notes

Sourced from io.github.raamcosta.compose-destinations:core's releases.

2.3.0

Main changes

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

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

2.2.0

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:

@Destination<RootGraph>
@Composable
fun MyScreen(
    resultRecipient: ResultRecipient<ConfirmationScreenDestination, Boolean>
) {
resultRecipient.onNavResult(
    deliverResultOn = OpenResultRecipient.DeliverResultOn.RESUME
) { result -&gt;
    // ...
}

}

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.

@Destination<RootGraph>(
    label = "my screen label"
</tr></table> 

... (truncated)

Commits

• de18a87 migration to central portal
• 33e5dfe fix lint
• d72e67b update README.md
• 5029370 update viewmodel factory stuff
• 772147c update compose 1.9
• 34a1381 Update README.md
• 98fd7ba fix build
• 13e61b8 Update README.md
• dfd2781 Fixes #736
• 602857d Fixes #728
• Additional commits viewable in compare view

Updates io.github.raamcosta.compose-destinations:ksp from 2.1.0 to 2.3.0

Release notes

Sourced from io.github.raamcosta.compose-destinations:ksp's releases.

2.3.0

Main changes

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

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

2.2.0

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:

@Destination<RootGraph>
@Composable
fun MyScreen(
    resultRecipient: ResultRecipient<ConfirmationScreenDestination, Boolean>
) {
resultRecipient.onNavResult(
    deliverResultOn = OpenResultRecipient.DeliverResultOn.RESUME
) { result -&gt;
    // ...
}

}

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.

@Destination<RootGraph>(
    label = "my screen label"
</tr></table> 

... (truncated)

Commits

• de18a87 migration to central portal
• 33e5dfe fix lint
• d72e67b update README.md
• 5029370 update viewmodel factory stuff
• 772147c update compose 1.9
• 34a1381 Update README.md
• 98fd7ba fix build
• 13e61b8 Update README.md
• dfd2781 Fixes #736
• 602857d Fixes #728
• Additional commits viewable in compare view

Updates io.github.raamcosta.compose-destinations:ksp from 2.1.0 to 2.3.0

Release notes

Sourced from io.github.raamcosta.compose-destinations:ksp's releases.

2.3.0

Main changes

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

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

2.2.0

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:

@Destination<RootGraph>
@Composable
fun MyScreen(
    resultRecipient: ResultRecipient<ConfirmationScreenDestination, Boolean>
) {
resultRecipient.onNavResult(
    deliverResultOn = OpenResultRecipient.DeliverResultOn.RESUME
) { result -&gt;
    // ...
}

}

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.

@Destination<RootGraph>(
    label = "my screen label"
</tr></table> 

... (truncated)

Commits

• de18a87 migration to central portal
• 33e5dfe fix lint
• d72e67b update README.md
• 5029370 update viewmodel factory stuff
• 772147c update compose 1.9
• 34a1381 Update README.md
• 98fd7ba fix build
• 13e61b8 Update README.md
• dfd2781 Fixes #736
• 602857d Fixes #728
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.