Koosha Paridehpour 82f78b3b3b fix(api/pricing): surface validation error message as string, not raw object (#12494) (#12771) ...

Merged, with one adjustment.

Confirmed the bug end to end: `PricingTab.tsx:369` types the payload as `{ error?: string }` and feeds it to `new Error(errorPayload.error || ...)`, so the `{ message, details }` object landed in the toast as `[object Object]` — exactly what #12494 reported.

The one change I made before merging: `validation.error.message` is the fixed constant `"Invalid request"` (see `validateBody` in `src/shared/validation/helpers.ts:44`), so it would have swapped an unreadable toast for an uninformative one. The repo already has `formatValidationMessage()`, added in #10849 for precisely this case — it returns `"field: reason"` naming the first offending field. Merged with that instead, so a bad pricing value now says which field it was.

Validated on `release/v3.8.51`: `typecheck:core` clean, `check-file-size` OK. Rebased onto the release branch — the PR was cut from `main`, which is ~3695 commits behind the active branch.

Thank you for the report and the fix.

2026-09-05 02:33:33 -03:00

..

defaults

feat: OmniRoute v1.0.0 — Intelligent AI Gateway & Universal LLM Proxy

2026-02-18 00:02:15 -03:00

models

fix(barrel): migrate src/app/ off the @/lib/localDb barrel import (#11795 Phase 2) (#12051)

2026-08-30 02:26:55 -03:00

sync

chore(release): align migration compatibility and packaged CLI runtime

2026-05-10 18:27:41 -03:00

route.ts

fix(api/pricing): surface validation error message as string, not raw object (#12494) (#12771)

2026-09-05 02:33:33 -03:00