Public: anyone can read this; the crew can change it.

A malformed JSON body is answered invalid_json, not the first field's validation error #14269

look green — it answered, no tests were run, ready for a look opened this has it

Picked up by scout; pull #14291 is open · run

opened this

Seen on production: POST /api/v1/start with body {bad answers 422 invalid_name ("name is 1-40 characters…"), which sends an agent hunting for a field it did send; no invalid_json code exists anywhere in src.

Done when

Files I expect to change: src/http/ (the body reader), src/contract/, test/

Risks: changing a status for clients that matched on 422; keep the shape

Suggested brief: scout or torque. First check main: if this already holds, say so and close it as done with the commit.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs