mirror of
https://github.com/BerriAI/litellm.git
synced 2026-08-28 05:25:59 +00:00
7ac95b1cee
* fix(ui): make hardcoded palette surfaces theme-aware Twenty-one dashboard files painted fills from the raw Tailwind palette with no dark counterpart, so in dark mode they rendered as near-white islands carrying dark text: unreadable. The route sweep caught them on teams, access-groups, policies, users, skills, guardrails-monitor, logs, compliance, playground, fallbacks and the AI hub. Where the hue already had a semantic token, the surface moves onto it. Every one of these lines had a token on its border and a palette class on its fill, so this finishes a migration that had stalled halfway: bg-blue-50 next to border-info/20 becomes bg-info, bg-gray-50 becomes bg-muted, DocLink's bg-white becomes bg-card, and the Alert error variant drops text-red-800 and text-red-600 for the destructive token its sibling variants already use. Purple, violet and indigo have no token in the system, which is exactly why the maps in PluginTableColumns, GuardrailsOverview, AccessGroupsTableColumns and teamTableColumns had migrated every other entry and left those behind. Rather than mint a brand token here, they take the dark palette step, matching what TeamGuardrailsTab, add_agent_form, MCPToolsetsTab and mcp_connect already do. Gradient stops get the same treatment since bg-linear stops have no token form. Light mode is unchanged apart from the four surfaces that moved onto a token, and those stay inside the same colour family. The #1e1e1e code slabs in guardrail_info and CustomCodeModal are deliberately left alone: they are intentionally dark editors in both themes, and their gray-200 text stays legible either way. * fix(ui): give dark surfaces a readable foreground step The dark fills added for the purple and indigo surfaces left three nested foregrounds on their original light-palette step, so the text and icon sitting on those new fills dropped below readable contrast in dark mode. text-purple-800 on purple-950 measured 1.72:1, text-indigo-600 on indigo-950 2.54:1, and text-purple-600 on the blue-950 gradient stop 2.73:1. Each now takes the purple-300 / indigo-300 step this PR already uses elsewhere, which lands them at 8.48:1, 8.02:1 and 8.31:1. The pricing calculator renders the same cost expression twice, so both copies move together rather than leaving one half-migrated. * fix(ui): keep the guardrail chip remove button visible on hover The chip itself moved to the dark indigo fill, but its remove button still darkened to indigo-900 on hover, which against indigo-950 measures 1.40:1 and makes the X vanish under the cursor in dark mode. Dark mode now brightens to indigo-100 on hover instead, mirroring the light theme where hover darkens away from the resting colour. |
||
|---|---|---|
| .. | ||
| litellm-dashboard | ||
| Dockerfile | ||
| nginx.conf | ||