Navigate using the app history when registered, otherwise React Router's
useNavigate.
Prefer this in shared plugin code that must run under both the new and old
frontend systems. Paths must start with / and exclude the deployment
basename. The old frontend fallback also accepts legacy route-ref URLs that
already include its configured basename. Relative paths belong to routing adapters and are rejected.
With app history, navigation reads the latest location when called, including
for empty, query-only, and hash-only targets. A number traverses that many history
entries. External URLs are supported when app history is registered; the old
frontend system retains React Router navigation semantics.
The react-aria-style counterpart to this hook is useAppHref.
Navigate using the app history when registered, otherwise React Router's
useNavigate.Prefer this in shared plugin code that must run under both the new and old frontend systems. Paths must start with
/and exclude the deployment basename. The old frontend fallback also accepts legacy route-ref URLs that already include its configured basename. Relative paths belong to routing adapters and are rejected. With app history, navigation reads the latest location when called, including for empty, query-only, and hash-only targets. A number traverses that many history entries. External URLs are supported when app history is registered; the old frontend system retains React Router navigation semantics.The react-aria-style counterpart to this hook is useAppHref.