litellm/ui
Mateo Wang 2bb8f7f219
fix(ui): label Decisions playground issues by question key and fix the Response header row (#46145)
* fix(ui): dedupe blank-question issues and label Decisions questions by key, not position

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* fix(ui): make the Response card header a flex row so title and badges share one line

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* test(ui): fail when duplicate blank-name issues stop being deduped

* fix(ui): drop the Decisions issue dedupe, which no reachable endpoint needs

* fix(ui): center the Response header and test the Decisions issue labels end to end

The card's border rule set 24px of bottom padding on the Response header, which put its content 8px above center. The header now keeps 8px on both sides. New tests cover the /v1/decisions position label and the score-level warning label for an all-digit key, which mutations of validatePayload left untested

* test(ui): check the Decisions Response header layout in the browser

* test(ui): register the Decisions header spec's model through the API so it runs in CI

The CI UI stack does not read fixtures/config.yml, so the config-only fake-decisions-model never existed there and the spec could not pick it. The spec now creates a uniquely named typesafe model against the mock server, waits until /model_group/info lists it as an evaluation model and /v1/systemone answers, and deletes it afterwards

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-10-14 10:47:05 -07:00
..
litellm-dashboard fix(ui): label Decisions playground issues by question key and fix the Response header row (#46145) 2026-10-14 10:47:05 -07:00
Dockerfile refactor(lens): connect LiteLLM to the independent Lens service (#45529) 2026-10-09 16:17:05 -07:00
nginx.conf fix(ui): boot the UI image as an arbitrary uid by anchoring nginx writes under /tmp (#37982) 2026-08-24 11:57:36 -07:00