Add strict input validation for predictions queries - #477
Merged
greatest0fallt1me merged 1 commit intoJul 25, 2026
Merged
Conversation
|
@code-0-stella Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Merged into main via admin resolver (-X theirs). |
Contributor
|
LGTM 👌 merging. Solid contribution. |
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.
Add strict input validation for predictions queries
PR Description
This change adds route-boundary validation for GET /api/predictions using a dedicated Zod schema.
What changed
Why
This makes predictions input handling consistent with the project’s other validated routes and ensures malformed requests fail fast with the standard 400 validation error envelope.
Verification
Ran ESLint on the touched files
Ran the predictions integration suite:
Closes: Add input validation for predictions (buffer #14) #350