mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-12 23:01:41 +00:00
5beb78fd1c
Most of the key edit payload is bound form fields, and the existing contract test pins those with a strict equality against a fixed object. Two keys are not fields: budget_fallbacks and tag_rpm_limit are computed in the submit handler from React state seeded off the loaded key, so a rewrite that moves that state can drop them without failing anything. budget_fallbacks had no coverage at all and tag_rpm_limit only appeared in the untouched-save constant, where it is an empty map either way. Pins that stored fallbacks and stored per-tag limits both survive an untouched save, and that a key with no fallbacks omits the field rather than sending an empty map, since the backend treats those differently. Verified by mutation: dropping the budget_fallbacks assignment reddens the resend case while correctly leaving the omit case green, and dropping the tag_rpm_limit assignment reddens its own case. |
||
|---|---|---|
| .. | ||
| litellm-dashboard | ||
| Dockerfile | ||
| nginx.conf | ||