Feature/jury panel#18
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (111)
📝 WalkthroughWalkthroughAdds jury assignments and criterion-based evaluations end-to-end: DB migrations and model changes, new FastAPI jury routes/dependencies/utils, updated schemas/admin, frontend API clients and jury UI with i18n and shared modal components, test coverage, and pytest marker configuration. ChangesEnd-to-end Jury Evaluation Feature
Sequence Diagram(s)sequenceDiagram
participant Frontend
participant API as backend.app.routes.jury
participant Utils as backend.app.utils.routes.jury
participant DB as Database
Frontend->>API: request assignments / submit evaluation / finish-evaluation
API->>DB: load/save JuryAssignment, SubmissionEvaluation, CriterionScore, Task
API->>Utils: finish_evaluation(task, assignments)
Utils->>DB: update assignment statuses, possibly update Task.status
API->>Frontend: return updated assignments/leaderboard
Estimated code review effort🎯 5 (Critical) | ⏱️ ~120 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches📝 Generate docstrings
|
Summary by CodeRabbit
New Features
Documentation
Improvements
Tests