Routing feature for Compose Web, Compose HTML and Desktop
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.13...v0.2.14
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.13...v0.2.14-1.6.0-beta01
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.12...v0.2.13
Compatibility release for Kotlin 1.8.20/Compose 1.4.0-rc03
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.11...v0.2.12
This is a technical release using Kotlin 1.8.0 and Compose for Web 1.3.0-rc02.
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.10...v0.2.11
Just updating Compose to 1.2.1 and Kotlin to 1.7.20
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.9...v0.2.10
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.8...v0.2.9
DesktopRouter, HashRouter, and BrowserRouter are now internal classes. Use the Composable functions instead. The reason is to prevent creating a new Router instance, which results in wrong navigation. Please create an issue with your use case if you need to instantiate a Router without actually adding it to the Composable hierarchy.
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.7...v0.2.8
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.6...v0.2.7
Instead hardcoding active
, it now possible to use the boolean lambda parameter for customization when the current path starts with to
.
NavLink(to = "/users", { isActive ->
if (isActive) {
classes("active")
}
}) {
Text("Users")
}
Full Changelog: https://github.com/hfhbd/routing-compose/compare/v0.2.5...v0.2.6