Refuse mistyped optional fields on POST /api/sandboxed with 400 - #514
Merged
davidmckayv merged 2 commits intoSep 13, 2026
Merged
Conversation
Ayush7614
requested review from
MikeRyanDev,
davidmckayv,
guidovizoso,
mxmzb and
tylerslaton
as code owners
September 13, 2026 05:12
davidmckayv
approved these changes
Sep 13, 2026
davidmckayv
left a comment
Contributor
There was a problem hiding this comment.
Deep-reviewed clean (validation, no secret leak, fail-closed, agrees with existing layers). CI green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Only slug and title were checked; description/html/css/jsFunctions flowed in as
?? ""and argumentSchema/sampleArguments as?? {}, so a number, array or JSON string travelled into a text/jsonb column and came back as an unhandled 500.Absent still means the default; a present text field must be a string (400
The component <field> must be text.) and a present schema field must be a plain object (400The component <field> must be an object.), before the store or the database sees the values.Tests: new server/tests/sandboxed-save-fields.test.ts (22 cases: defaults, well-typed save, 10 non-string text shapes, 9 non-object schema shapes, mixed-body atomicity). Verified: sandboxed routes + save-fields suites — 26 pass.