0.0.14

What is new

Routing Core

To check if a route is registered before invoking it, you can use Routing.canHandleByName or Routing.canHandleByPath methods, depending on how your routing is set up. These methods help determine if a given route name or path matches any registered routes, allowing you to handle navigation appropriately. lookUpOnParent parameter helps with nested routing look up.

Routing Resources

Type-safe routing also received a support to check if a route is registered

JavaScript integration

Web applications has different history modes, specifically hash-based (/#/) and HTML5 history API. These modes facilitate handling navigation history in single-page applications (SPAs).

1. Hash-based Routing: In hash-based routing, the URL contains a hash fragment (/#/) followed by the route. This method doesn't trigger a full page reload when navigating between routes, making it suitable for SPAs. It's compatible with older browsers and doesn't require server-side configuration.
2. HTML5 History API: This API allows manipulating the browser history using JavaScript, enabling more natural-looking URLs without hash fragments. It's more modern and provides cleaner URLs but requires server-side configuration to handle URL requests properly.
3. In-memory: Memory routing typically doesn't involve changing the URL and is often used in testing or scenarios where navigation doesn't need to be reflected in the browser's address bar.

Full Changelog: 0.0.13...0.0.14

0.0.13

What is new

• Android Activity integration. Check android-activity sample for more details
• Apple UIKit integration. Check ios-sample for more details

Changes

• Core module now export better functions name and parameters to Objective-C

Full Changelog: 0.0.12...0.0.13

0.0.12

What is new

• Compose Animation module to support animated routing

Changes

• Pop result now can be caught by the Routing instead of Local Composition
• Improvements and fixes

Full Changelog: 0.0.11...0.0.12

Version 0.0.11

• Removed core-stack module. Each framework/platform will use your own stack behaviors
• Route methods simplified
• Web Browser History support to javascript module

Full Changelog: 0.0.10...0.0.11

Version 0.0.10

New features

• Voyager support is back
• State restoration
• Compose Multiplatform
• Basic support to web history

Upgrades

• Gradle 8.5
• Kotlin 1.9.21 - to avoid API breaking changes with Voyager
• Kotlin Serialization 1.6.2
• Kotlin Coroutines 1.8.0-RC2
• Ktor 3.0.0-beta-1
• Android Gradle Plugin 8.2.1
• KTLint 12.1.0
• Kotlin Kover 0.7.5

Other

• Added extension function call to Routing that easily create an application call
• Added Kotlin Serialization to handle state restoration
• Added support to unregister a route created using Ktor Resources
• Added support to notify previous route when current will be popped.
• Check commits for more

Full Changelog: 0.0.8...0.0.10

Version 0.0.9

Avoid and jump to 0.0.10

Version 0.0.8

• Added Call Logging plugin
• Added Session plugin
• Added Authentication plugin
• MDC partial support
• Support for Monitoring Event

Full Changelog: 0.0.7...0.0.8

Version 0.0.7

• Fix path compare using startsWith that was not good when child path starts with rootPath value.

Full Changelog: 0.0.6...0.0.7

Version 0.0.6

• Improvements to Nested Routing support
• Convert events module to support Nested Routing

Full Changelog: 0.0.5...0.0.6

Version 0.0.5

• Downgrade JVM toolchains and bytecode to Java 1.8
• Removed modules not related to routing
• Voyager modules will be implemented on it official repo to avoid breaking changes

Full Changelog: 0.0.4...0.0.5