[codex] add input length guards#225
Closed
saurabhhhcodes wants to merge 1 commit into
Closed
Conversation
Contributor
|
Someone is attempting to deploy a commit to the Sunil Kumar's projects Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
Closing this as a duplicate of the already-open input-limit PR #183 so we avoid overlapping work. |
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.
What changed
Why
The app was accepting free-form input without clear length guardrails. That created a mismatch between the UI and server expectations and left room for invalid payloads.
Impact
Users now get immediate feedback in the UI, and the backend rejects invalid requests consistently.
Validation
git diff --checknode --check server/src/routes/chat.jsnode --check server/src/routes/servers.jsnpm run buildinfrontendCloses #135