Replace Term Confusion Pairs with Review Events - #10
Conversation
- Remove `termConfusionPairs` table and related API methods. - Introduce `reviewEvents` table to record detailed data for every practice test question attempt. - Implement logic to calculate `answeredTermId` for MCQ and TFQ questions. - Ensure `reviewEvents` are updated when a practice test question is modified. - Clean up the codebase by removing obsolete types, methods, and tests. - Update database schema to version 19.
|
👋 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. |
1 participant
This change replaces the old and inaccurate "term confusion pairs" tracking with a new
reviewEventssystem.Key improvements:
ReviewEventrecord, capturing whether it was correct, the question type, the answer provided (term ID or string), and the activity type.term_confusion_pairstable is removed, and a new migration adds thereviewEventstable.recordConfusionPairs,getTopConfusionPairs, etc.) and cleaned up term resolution logic.confusion_pairs.spec.tstest file as it no longer applies. Verified that existing practice test functionality remains correct through automated tests.PR created automatically by Jules for task 11668912116007394987 started by @ehanahamed