Skip to content

v5.1.3

Choose a tag to compare

View all tags
@7PH 7PH released this 11 Sep 23:14
· 54 commits to master since this release
v5.1.3
25e2bef

v5.1.3

  • Released: 2026-09-11
  • Summary: Patch. Form validation errors reached the client as a generic failure instead of the field-level message the backend already built.

Upgrade Notes

No action required. No schema, API, or migration changes. The 400 validation response keeps its existing error and message keys and only gains a detail key alongside them.

Bug Fixes

Validation errors showed "something went wrong"

The RequestValidationError handler formatted a per-field message (field: reason) and returned it under message, but useApi's apiFetch only reads detail — the key the HTTPException handler uses. The formatted text was dropped and every 400 validation failure surfaced as a generic error. The handler now returns the same text under detail as well.

Assets 2
Loading