fix(web): redirect authenticated login route
CI / publish (push) Failing after 4s
CI / verify (push) Successful in 9m29s

This commit is contained in:
karti-ai
2026-08-28 12:22:23 -07:00
parent 8a6601dfce
commit 162c8a2378
+6 -7
View File
@@ -244,13 +244,11 @@ function AppRoutes() {
{/* {/*
`/` is the front door, and the front door is Piggy. `/` is the front door, and the front door is Piggy.
-------------------------------------------------- --------------------------------------------------
Signing in does not navigate: the auth gate simply starts rendering Signing in does not navigate from the form: the auth gate starts
these routes at whatever address the browser is already on, which for rendering these routes at the browser's current address. `/` goes to
anyone arriving fresh is `/`. So "land on Piggy after sign-in" and Piggy directly, while `/login` has its own authenticated-only redirect
"`/` is Piggy" are the same sentence, and this is the only line that below so a person who used the explicit sign-in URL does not land on
decides it. A post-sign-in `navigate()` was rejected: it fires on one the catch-all Not found page.
path through the gate and not on a hard refresh, so the product would
open somewhere different depending on how you got there.
It is a redirect rather than Piggy mounted at the index, because the It is a redirect rather than Piggy mounted at the index, because the
workspace needs ONE address. Two paths rendering it would leave the workspace needs ONE address. Two paths rendering it would leave the
@@ -273,6 +271,7 @@ function AppRoutes() {
into them still resolve directly, with no pass through here. into them still resolve directly, with no pass through here.
*/} */}
<Route index element={<Navigate to="/piggy" replace />} /> <Route index element={<Navigate to="/piggy" replace />} />
<Route path="login" element={<Navigate to="/" replace />} />
<Route path="overview" element={<RoutePage><Overview /></RoutePage>} /> <Route path="overview" element={<RoutePage><Overview /></RoutePage>} />
<Route path="margin" element={<RoutePage><Margin /></RoutePage>} /> <Route path="margin" element={<RoutePage><Margin /></RoutePage>} />
<Route path="growth" element={<RoutePage><Growth /></RoutePage>} /> <Route path="growth" element={<RoutePage><Growth /></RoutePage>} />