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