✨ Feature Description
Design and implement a new SQLAlchemy model, QuestComment, for managing comments related to individual coding quests. This model should enforce a 1-to-1 relationship with the coding_quests table and track the author, comment text, and creation time.
🧩 Problem Statement
Currently, there is no comment-tracking feature connected to quests. Adding the QuestComment model enables feedback, notes, or additional info for each coding quest.
💡 Proposed Solution
- Create a new
QuestComment model/class.
- Include a 1:1 relationship with the existing
coding_quests model (using quest_id as foreign key, ensuring each quest has at most one comment record).
- Fields:
id: Primary key, UUID or integerquest_id: Foreign key to coding_quests, enforce uniquenesscomment_author: UserId of the author's comment (string, required): Relation with users table 1-to-1comment: Text of the comment (required)created_at: Date/time of creation (default current timestamp)
📋 Acceptance Criteria
✨ Feature Description
Design and implement a new SQLAlchemy model,
QuestComment, for managing comments related to individual coding quests. This model should enforce a 1-to-1 relationship with thecoding_queststable and track the author, comment text, and creation time.🧩 Problem Statement
Currently, there is no comment-tracking feature connected to quests. Adding the
QuestCommentmodel enables feedback, notes, or additional info for each coding quest.💡 Proposed Solution
QuestCommentmodel/class.coding_questsmodel (using quest_id as foreign key, ensuring each quest has at most one comment record).id: Primary key, UUID or integerquest_id: Foreign key to coding_quests, enforce uniquenesscomment_author: UserId of the author's comment (string, required): Relation with users table 1-to-1comment: Text of the comment (required)created_at: Date/time of creation (default current timestamp)📋 Acceptance Criteria