Routing

The decision model that governs route resolution and navigation behavior.

Core Structure

Intor models routing as two complementary core components:

Inbound
Resolves locale, pathname, and related request context
Outbound
Derives navigation targets and navigation behavior

Path

A path describes how locale information is structurally represented in a URL and serves as the shared foundation for both Inbound and Outbound routing.

Its concrete representation is influenced by localePrefix and basePath.

For configuration details, see: localePrefix , basePath

Path Transformation Model

Paths are handled through a transformation model rather than treated as raw strings.

localizePathname is the core implementation of this model and is exposed as a public API.

The transformation pipeline consists of the following steps:

Canonicalize → Standardize → Materialize

The transformation result provides three different path representations:

• canonicalPathname: The path with basePath and locale prefixes removed.
• templatedPathname: A template path where the locale position is represented by {locale}.
• pathname: The final, materialized path with locale and routing rules applied.