fix: use absolute path for /deployments redirect
All checks were successful
CI / cleanup-branch (push) Has been skipped
CI / build (push) Successful in 2m14s
CI / cleanup-branch (pull_request) Has been skipped
CI / build (pull_request) Successful in 2m4s
CI / docker (pull_request) Has been skipped
CI / docker (push) Successful in 34s
CI / deploy (pull_request) Has been skipped
CI / deploy-feature (pull_request) Has been skipped
CI / deploy (push) Has been skipped
CI / deploy-feature (push) Successful in 26s
All checks were successful
CI / cleanup-branch (push) Has been skipped
CI / build (push) Successful in 2m14s
CI / cleanup-branch (pull_request) Has been skipped
CI / build (pull_request) Successful in 2m4s
CI / docker (pull_request) Has been skipped
CI / docker (push) Successful in 34s
CI / deploy (pull_request) Has been skipped
CI / deploy-feature (pull_request) Has been skipped
CI / deploy (push) Has been skipped
CI / deploy-feature (push) Successful in 26s
The relative `to="apps"` didn't resolve correctly. All other legacy redirects use absolute paths (`to="/apps"`, `to="/runtime"`). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -65,7 +65,7 @@ export const router = createBrowserRouter([
|
||||
{ path: 'logs/:appId/:routeId', element: <Navigate to="/runtime" replace /> },
|
||||
{ path: 'config', element: <Navigate to="/apps" replace /> },
|
||||
{ path: 'config/:appId', element: <Navigate to="/apps" replace /> },
|
||||
{ path: 'deployments', element: <Navigate to="apps" replace /> },
|
||||
{ path: 'deployments', element: <Navigate to="/apps" replace /> },
|
||||
|
||||
// Apps tab (OPERATOR+ via UI guard, shows all or single app)
|
||||
{ path: 'apps', element: <SuspenseWrapper><AppsTab /></SuspenseWrapper> },
|
||||
|
||||
Reference in New Issue
Block a user