fix(server): reject whitespace-only and non-string slug and title in POST /sandboxed - #387
Open
Ayush7614 wants to merge 1 commit into
Open
Conversation
Ayush7614
requested review from
MikeRyanDev,
davidmckayv,
guidovizoso and
tylerslaton
as code owners
September 5, 2026 19:47
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
1 participant
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.
POST /api/sandboxed accepted a whitespace-only or non-string slug/title: the truthiness guard let
" "and123through, storing a blank title verbatim or failing later with a misleading error (or a 500 on a non-string title).Rejects non-string and whitespace-only slug/title with 400 and trims both before save, mirroring the POST /servers/custom validation. Verified with an 8-case guard script (whitespace, numeric, null, padded inputs) and server typecheck.