Route page stats: format durations and latencies to user locale #65

Closed
opened 2026-03-14 22:24:40 +01:00 by claude · 1 comment
Owner

Problem

Avg Duration and P99 Latency values in RouteHeader and PerformanceTab are displayed as raw numbers (e.g. 312ms) without locale formatting. Other stats like Executions Today already use toLocaleString().

Expected

All numeric stat values should use toLocaleString() for the user's locale — e.g. 1,312ms instead of 1312ms.

Files

  • ui/src/pages/routes/RouteHeader.tsx — header stat boxes
  • ui/src/pages/routes/PerformanceTab.tsx — stat cards
## Problem Avg Duration and P99 Latency values in RouteHeader and PerformanceTab are displayed as raw numbers (e.g. `312ms`) without locale formatting. Other stats like Executions Today already use `toLocaleString()`. ## Expected All numeric stat values should use `toLocaleString()` for the user's locale — e.g. `1,312ms` instead of `1312ms`. ## Files - `ui/src/pages/routes/RouteHeader.tsx` — header stat boxes - `ui/src/pages/routes/PerformanceTab.tsx` — stat cards
Author
Owner

Closing as stale — referenced files (RouteHeader.tsx, PerformanceTab.tsx) no longer exist after route pages were rewritten. Locale formatting consistency is tracked more broadly in #110.

Closing as stale — referenced files (`RouteHeader.tsx`, `PerformanceTab.tsx`) no longer exist after route pages were rewritten. Locale formatting consistency is tracked more broadly in #110.
Sign in to join this conversation.