Resolves an app-absolute path to a browser-ready href (including the app's
deploy basename), the react-aria-style counterpart to useAppNavigate.
Falls back to React Router when no coreApis.appHistory is registered
(old frontend system).
Paths must start with / and are relative to the app root, excluding the
deployment basename. The old frontend fallback also accepts legacy route-ref
URLs that include its configured basename. Empty, query-only, and hash-only
targets use the current path.
Relative paths belong to routing adapters and are rejected by this hook.
External URLs are returned unchanged.
A target whose scheme a browser executes rather than navigates to —
javascript:, data: or vbscript:, however it is spelled — is replaced
with about:blank and a warning, so an href built from a catalog annotation
or any other value the app does not control cannot run script when it is
clicked. Every other scheme, mailto: and tel: included, is left alone.
Resolves an app-absolute path to a browser-ready href (including the app's deploy basename), the react-aria-style counterpart to useAppNavigate.
Falls back to React Router when no coreApis.appHistory is registered (old frontend system).
Paths must start with
/and are relative to the app root, excluding the deployment basename. The old frontend fallback also accepts legacy route-ref URLs that include its configured basename. Empty, query-only, and hash-only targets use the current path. Relative paths belong to routing adapters and are rejected by this hook. External URLs are returned unchanged.A target whose scheme a browser executes rather than navigates to —
javascript:,data:orvbscript:, however it is spelled — is replaced withabout:blankand a warning, so an href built from a catalog annotation or any other value the app does not control cannot run script when it is clicked. Every other scheme,mailto:andtel:included, is left alone.