Skip to content

Releases: raamcosta/compose-destinations

2.2.0

03 May 12:10
98fd7ba
Compare
Choose a tag to compare

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 ->
        // ...
    }
}

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"
)
@Composable
fun MyScreen() {
}

Full Changelog: 2.1.1...2.2.0

2.1.0 - First non beta of v2!

06 Mar 14:28
42b0514
Compare
Choose a tag to compare

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

Full Changelog: 2.1.0-beta16...2.1.0

2.1.0-beta16

30 Jan 17:28
fdd5a26
Compare
Choose a tag to compare
2.1.0-beta16 Pre-release
Pre-release

Changes

  • Dependency updates

Full Changelog: 2.1.0-beta15...2.1.0-beta16

1.11.9

30 Jan 17:28
10eecbc
Compare
Choose a tag to compare

Changes

  • Dependency updates

Full Changelog: 1.11.8...1.11.9

2.1.0-beta15

22 Dec 02:01
ed73aab
Compare
Choose a tag to compare
2.1.0-beta15 Pre-release
Pre-release

What's Changed

New Contributors

  • @Rawa made their first contribution in #708

Full Changelog: 2.1.0-beta14...2.1.0-beta15

1.11.8

22 Dec 02:00
40b968c
Compare
Choose a tag to compare

Changes

  • Dependency updates

Full Changelog: 1.11.7...1.11.8

2.1.0-beta14

17 Oct 14:34
0920105
Compare
Choose a tag to compare
2.1.0-beta14 Pre-release
Pre-release

Changes

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

Full Changelog: 2.1.0-beta13...2.1.0-beta14

2.0.0-beta12

17 Oct 14:34
90e9a8b
Compare
Choose a tag to compare
2.0.0-beta12 Pre-release
Pre-release

Changes

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

Full Changelog: 2.0.0-beta11...2.0.0-beta12

1.11.7

10 Oct 10:15
668cff6
Compare
Choose a tag to compare

Changes

  • Updated dependencies to latest stable

Full Changelog: 1.11.6...1.11.7

2.1.0-beta12

11 Sep 08:38
c731ff9
Compare
Choose a tag to compare
2.1.0-beta12 Pre-release
Pre-release

Changes

  • Update dependencies to Compose 1.7 and Compose Navigation 2.8 by @extmkv in #680

Full Changelog: 2.1.0-beta11...2.1.0-beta12