search

foodiestudio / devtools

provide a simple `Debug Entrance`
MIT License
0 stars 0 forks source link

chore(deps): bump composeDestinations from 1.7.32-beta to 1.9.50 #23

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps composeDestinations from 1.7.32-beta to 1.9.50. Updates io.github.raamcosta.compose-destinations:animations-core from 1.7.32-beta to 1.9.50

Release notes

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

1.9.50 No longer beta! 🙌 No more accompanist-navigation! 🎉

Removed accompanist navigation since animations were imported to official compose navigation! 🎉

Because of this, some minor changes had to be made:

  • DestinationStyleAnimated -> DestinationStyle.Animated
  • rememberAnimatedNavHost -> rememberNavHost
  • rememberAnimatedNavHostEngine -> rememberNavHostEngine (unless you are using bottom sheet destinations, in which case you still need to use rememberAnimatedNavHostEngine)
  • ExperimentalAnimationApi removed on most APIs
  • If you were not using DestinationsNavHost:
    • AnimatedNavHost -> NavHost
    • animatedComposable -> composable
  • You no longer need animations-core unless you are using BottomSheet destinations (which still is using accompanist material under the hood)
  • If you do still use animations-core, even if you don't need BottomSheet, it's totally fine, using rememberAnimatedNavHostEngine will just internally call rememberNavHostEngine.

No beta suffix? 🤔

Yes, that's right, there were a lot of insecurities hiding behind that "-beta" suffixed on all the lib's versions. The truth is that API changes might happen but each version is stable for production. This is especially annoying because some developers have company policies that state they cannot use this library because of this. So from now on, if big changes happen I will create alpha, beta, rc releases (not necessarily all three, as it seems quite unnecessary most of the time) related to that specific version, basically following practices that you might be used to with other jetpack libraries and such.

Thanks for being with me through this time, Compose Destinations is just getting started! Look forward to v2 which I honestly think will be great!

1.9.42-beta

Fixes

  • Fixed #415 - issue that was happening if you were not using animations core.

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.41-beta...1.9.42-beta

1.9.39-beta

  • Compose 1.5 support 🙌

1.8.41-beta

Changes

  • Added ability to use @Destination on other annotation classes which can then be used on the composable functions, transferring all their options this way.

Example:


@Destination(
    deepLinks = [
        DeepLink(
            uriPattern = ...,
        ),
        DeepLink(
            uriPattern = ...,
        )
    ],
</tr></table>

... (truncated)

Commits


Updates io.github.raamcosta.compose-destinations:ksp from 1.7.32-beta to 1.9.50

Release notes

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

1.9.50 No longer beta! 🙌 No more accompanist-navigation! 🎉

Removed accompanist navigation since animations were imported to official compose navigation! 🎉

Because of this, some minor changes had to be made:

  • DestinationStyleAnimated -> DestinationStyle.Animated
  • rememberAnimatedNavHost -> rememberNavHost
  • rememberAnimatedNavHostEngine -> rememberNavHostEngine (unless you are using bottom sheet destinations, in which case you still need to use rememberAnimatedNavHostEngine)
  • ExperimentalAnimationApi removed on most APIs
  • If you were not using DestinationsNavHost:
    • AnimatedNavHost -> NavHost
    • animatedComposable -> composable
  • You no longer need animations-core unless you are using BottomSheet destinations (which still is using accompanist material under the hood)
  • If you do still use animations-core, even if you don't need BottomSheet, it's totally fine, using rememberAnimatedNavHostEngine will just internally call rememberNavHostEngine.

No beta suffix? 🤔

Yes, that's right, there were a lot of insecurities hiding behind that "-beta" suffixed on all the lib's versions. The truth is that API changes might happen but each version is stable for production. This is especially annoying because some developers have company policies that state they cannot use this library because of this. So from now on, if big changes happen I will create alpha, beta, rc releases (not necessarily all three, as it seems quite unnecessary most of the time) related to that specific version, basically following practices that you might be used to with other jetpack libraries and such.

Thanks for being with me through this time, Compose Destinations is just getting started! Look forward to v2 which I honestly think will be great!

1.9.42-beta

Fixes

  • Fixed #415 - issue that was happening if you were not using animations core.

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.41-beta...1.9.42-beta

1.9.39-beta

  • Compose 1.5 support 🙌

1.8.41-beta

Changes

  • Added ability to use @Destination on other annotation classes which can then be used on the composable functions, transferring all their options this way.

Example:


@Destination(
    deepLinks = [
        DeepLink(
            uriPattern = ...,
        ),
        DeepLink(
            uriPattern = ...,
        )
    ],
</tr></table>

... (truncated)

Commits


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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #26.