Skip to content

feat: better validation errors - #6848

Draft
Flo4604 wants to merge 1 commit into
mainfrom
flo-validation-errors
Draft

feat: better validation errors#6848
Flo4604 wants to merge 1 commit into
mainfrom
flo-validation-errors

Conversation

@Flo4604

@Flo4604 Flo4604 commented Jul 25, 2026

Copy link
Copy Markdown
Member

Problem:

 Our validation errors dont read nicely

Solution:

 Write custom error messages instead of relying on the ones we get from our openapi pkg.

Impact:

 None

Testing:

Tests should pass + there is a file showing all the new validation errors with before/after.

@vercel

vercel Bot commented Jul 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dashboard Ready Ready Preview, Comment Jul 27, 2026 4:12pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
design Ignored Ignored Preview Jul 27, 2026 4:12pm

Request Review

@Flo4604
Flo4604 changed the base branch from flo-wllmsytzowpu to flo-spec-redaction July 25, 2026 20:03
@Flo4604 Flo4604 changed the title Flo validation errors feat: better validation errors Jul 25, 2026
@Flo4604
Flo4604 force-pushed the flo-spec-redaction branch from 5ed47f3 to e3ec671 Compare July 27, 2026 10:39
Base automatically changed from flo-spec-redaction to main July 27, 2026 12:00
@Flo4604
Flo4604 force-pushed the flo-validation-errors branch from b3f7cf4 to db15d21 Compare July 27, 2026 12:09
@Flo4604
Flo4604 force-pushed the flo-validation-errors branch from db15d21 to 11ca4b2 Compare July 27, 2026 12:19
@Flo4604
Flo4604 force-pushed the flo-validation-errors branch from 11ca4b2 to 6a7271c Compare July 27, 2026 12:45
@Flo4604
Flo4604 force-pushed the flo-validation-errors branch from 6a7271c to 2d4809f Compare July 27, 2026 15:55
@Flo4604
Flo4604 force-pushed the flo-validation-errors branch from 2d4809f to 622d378 Compare July 27, 2026 16:04
Validation errors named the schema keyword pointer rather than the field that
failed, reported only the first of a request's problems, and were assembled by
regex over the library's prose. Messages are now built from jsonschema's typed
error kinds, reading only the constraint side, so location points at the caller's
field and every failure is reported.

  before  /properties/variables/items/properties/value/pattern
          does not satisfy 'pattern'
  after   body.variables[1].key
          must match the pattern '^[A-Za-z_][A-Za-z0-9_]*$'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant