fix(comment/create): validate request body with a zod schema - #1469
fix(comment/create): validate request body with a zod schema#1469rajanpanth wants to merge 1 commit into
Conversation
createComment received req.body unvalidated: message had only a client-side length limit (so the API accepted very large strings) and refType/type/ref ids were unchecked. Add a zod schema that enforces message length (1-280), validates refType/type against their enums, and types the id fields, rejecting invalid payloads with 400.
|
@rajanpanth is attempting to deploy a commit to the Superteam Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
Next review available in: 57 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
createCommentreceivedreq.bodyunvalidated:messagehad only a client-side length limit (so the API accepted very large strings) andrefType/type/ref ids were unchecked.Adds a zod schema enforcing message length (1–280, matching the client limit), validating
refType/typeagainst their Prisma enums, and typing the id fields. Invalid payloads get a 400.Uses the same
z.nativeEnum(...)pattern already used elsewhere in the repo (e.g.ai-generate/*routes).pnpm check-typesandpnpm lintpass.