feat: Add QuestBriefSchema fields to quest creation API (#257) - #447
Open
Adil2009700 wants to merge 6 commits into
Open
feat: Add QuestBriefSchema fields to quest creation API (#257)#447Adil2009700 wants to merge 6 commits into
Adil2009700 wants to merge 6 commits into
Conversation
added 6 commits
July 5, 2026 23:24
…#410) - Add questSubmissions include to getAssignments API to fetch latest submission data - Create ReworkFeedbackPanel component to display criteria results, quality score, and reviewer notes - Show feedback panel when assignment status is 'needs_rework' - Handle graceful fallback when no feedback data is available
… Wrap handleApprove and handleReject in try/catch blocks - Check HTTP response status and JSON success flag - Display error toast on failure, success toast on success - Use finally block to ensure loading state is reset
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
|
The QuestBriefSchema fields in |
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
2 participants
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.
Fixes #257 ## Problem QuestBriefSchema structured fields were defined in Prisma schema but not used by API. ## Solution Updated quest creation/update API to accept all QuestBriefSchema fields: - submissionInstructions, expectedDeliverables, attachments, clientResources - problemStatement, starterRepo, estimatedHours, squadSize, ipTerms, clientOrg ## Impact - Companies can provide structured quest briefs via API - Enables AI PM layer to parse/decompose quests - Students get clearer context and deliverables ## Next Steps 1. Update frontend forms to include structured fields 2. Update quest detail pages to display structured fields 3. Update TypeScript types to include new fields