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).
This commit is contained in:
Anso
2026-05-19 23:25:30 -04:00
committed by GitHub
parent 9362c7215e
commit 0117556bea
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -99,7 +99,7 @@ export function FleetView({ onNavigateToNode }: FleetViewProps) {
{isAdmiral && (
<TabsHighlightItem value="routing">
<TabsTrigger value="routing">
<ArrowLeftRight className="w-4 h-4 mr-1.5" />Traffic
<ArrowLeftRight className="w-4 h-4 mr-1.5" />Routing
</TabsTrigger>
</TabsHighlightItem>
)}