Unleash / unleash / 26509634955

87%

master: 91%

push

github

chore: update react router step 1: relativeSplatPath (#12080)

Part of the gradual migration to React Router v7. Opts the app into v7's
`relativeSplatPath` behavior behind an internal flag
(`reactRouter_v7_relativeSplatPath`) so we can roll it out controllably
and fall back if something regresses in production.

## What this does

- Adds a new internal feature flag `reactRouter_v7_relativeSplatPath`
(defaults off in OSS, on in dev).
- Wires the flag to `<BrowserRouter future={{ v7_relativeSplatPath }}>`
in `frontend/src/index.tsx`.
- Pins the flag to `true` in `testRenderer.tsx` so tests run under the
new behavior.
- Fixes one site that broke under the new resolution semantics: the
project-settings vertical tabs in `ProjectSettings.tsx`. Both the
`onChange` handler and the catch-all `<Navigate>` were passing relative
tab IDs (`'access'`, `''`, etc.) into `navigate`/`<Navigate>`. Under v7
these append to the current URL instead of resolving against the route
mount; switched them to absolute paths derived from `location.pathname`.

## Why

Under v7, `navigate('access')` from `/projects/X/settings/segments`
resolves to `/projects/X/settings/segments/access` (appending) rather
than `/projects/X/settings/access` (replacing). This is the v7-correct
behavior — splat captures are no longer silently stripped during
relative-path resolution — but it surfaced a latent bug in the settings
tab navigation that was relying on the old (buggy) v6 behavior.

## Migration reference

- React Router v6 → v7 upgrade guide for this flag:
https://reactrouter.com/upgrading/v6#v7_relativesplatpath
- `useResolvedPath` docs explaining the resolution change:
https://reactrouter.com/6.30.3/hooks/use-resolved-path#splat-paths

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

1852 of 2047 branches covered (90.47%)

15118 of 17352 relevant lines covered (87.13%)

920.61 hits per line