From 0117556beab91e0845e81da079f1e3009df2a8d4 Mon Sep 17 00:00:00 2001 From: Anso Date: Tue, 19 May 2026 23:25:30 -0400 Subject: [PATCH] fix(fleet): rename Traffic tab label to Routing for consistency (#1119) The Fleet view sub-tab that renders RoutingTab.tsx was labeled "Traffic" while every adjacent identifier already used "Routing": the backend route file (backend/src/routes/mesh.ts), the component path, the localStorage key (sencho-routing-view-mode), the SegmentedControl aria label ("Routing view mode"), and the engineering vocabulary across the codebase. Operators looking for the "Routing tab" could not find it because the visible label said something else. Align the user-visible label with the rest of the implementation and update the two doc references that named the tab by its old label (docs/features/fleet-actions.mdx, .env.example). --- .env.example | 2 +- docs/features/fleet-actions.mdx | 2 +- frontend/src/components/FleetView.tsx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.env.example b/.env.example index e6770041..a601f35d 100644 --- a/.env.example +++ b/.env.example @@ -106,7 +106,7 @@ SSO_CALLBACK_URL= # Experimental UI surfaces. When unset or any value other than "true", # the UI hides surfaces that are kept in the repo but not yet promoted -# to the default 1.0 build (Fleet Traffic · Routing tab, Fleet +# to the default 1.0 build (Fleet Routing tab, Fleet # Deployments / Blueprints tab, Fleet Federation tab, Fleet Secrets # sync tab, Fleet Actions tab). Backend routes for these surfaces stay # live regardless. This flag controls UI discovery only. diff --git a/docs/features/fleet-actions.mdx b/docs/features/fleet-actions.mdx index d0b21c1e..1f712f41 100644 --- a/docs/features/fleet-actions.mdx +++ b/docs/features/fleet-actions.mdx @@ -7,7 +7,7 @@ description: Run fleet-wide bulk operations from one place — stop stacks acros Fleet Actions require a Sencho **Skipper** or **Admiral** license. -The **Fleet Actions** tab inside Fleet centralizes bulk operations that span more than a single stack and would otherwise need many manual clicks. It lives next to **Deployments** and **Traffic** in the Fleet view, after the separator that follows Status. +The **Fleet Actions** tab inside Fleet centralizes bulk operations that span more than a single stack and would otherwise need many manual clicks. It lives next to **Deployments** and **Routing** in the Fleet view, after the separator that follows Status. Fleet Actions covers the operations that aren't already exposed elsewhere in Sencho: diff --git a/frontend/src/components/FleetView.tsx b/frontend/src/components/FleetView.tsx index d704ab0b..a739396d 100644 --- a/frontend/src/components/FleetView.tsx +++ b/frontend/src/components/FleetView.tsx @@ -99,7 +99,7 @@ export function FleetView({ onNavigateToNode }: FleetViewProps) { {isAdmiral && ( - Traffic + Routing )}