🧹 Add doubt resolver organization validation#50
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Deployment failed with the following error: Learn More: https://vercel.com/gautams-projects-ba8db9e9?upgradeToPro=build-rate-limit |
🎯 What: Replaced a TODO comment in the doubt resolution logic with an actual database query to validate that the resolver (mentor) belongs to the same organization as the mentee's bootcamp.
💡 Why: This enforces organizational boundaries for resolving doubts and avoids exposing an API flaw that trusted the caller entirely. Using
sqlc.argcorrectly allowed generating an appropriately named Go struct.✅ Verification: Regenerated
sqlcmodels, updated service tests and successfully ran unit tests and lints locally under Go 1.25.0 as instructed.✨ Result: Improved security and logic completeness.
PR created automatically by Jules for task 10487586464920150896 started by @Gautam7352