From 09fdf530e13733e099d852edd5ae77908cdbd1b5 Mon Sep 17 00:00:00 2001 From: Gabriel Ittner Date: Wed, 12 Jun 2024 13:44:42 +0200 Subject: [PATCH] Changelog for 0.26.0 --- CHANGELOG.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 253c2deb8..3f25b92f9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,31 @@ Change Log ========== +## 0.26.0 *(2024-06-12)* + +### Navigation + +- Introduces `HostNavigator`. This was previously an internal type used within + `NavHost` to execute navigation events. It's now possible to create a + `HostNavigator` with `rememberHostNavigator(...)`, pass that instance to `NavHost` + and use it to navigate directly without the use of navigation events. It is safe + to reference `HostNavigator` outside the UI layer. +- `DestinationNavigator` is a replacement for `NavEventNavigator` that delegates + to `HostNavigator`, which means it also works without navigation events. The + advantage of using this over using `HostNavigator` directly is that + `DestinationNavigator` supports activity results, which `HostNavigator` doesn't. +- The `navigate {}` function that allows grouping multiple navigation events + is now more efficient. The `NavHost` will only be updated once at the end and + not between the actions of such a group. +- `NavEventNavigator` will be removed in one of the next releases. + +### Codegen + +- A `HostNavigator` is automatically created in the `NavHostActivity` component. +- It's required that a `NavRoot` is provided into the scope of a `NavHostActivity`. +- Each `NavDestination` now requires an `ActivityResultNavigator` to be provided into + the scope (previously `NavEventNavigator` was required). + ## 0.25.0 *(2024-05-17)* ### Navigation