Repository navigation
Task Management #4
Description
Dependencies: None.
Scope: Implement CRUD for the Task model.
Validation: Require strict chronological validation upon creation/update (e.g., registration_start_at < registration_end_at, submissions_start_at < submissions_end_at).
AND after that:
All tasks and hackathon services / URLs must be prefixed with hackathon, e.g. /tasks/hackathon/create
Scope: Implement an internal service that automatically generates a HackathonTask extension record within the same database transaction whenever a Task with task_type=HACKATHON is created. Create an endpoint to update the requirements_document_url.
Metadata
Metadata
Assignees
Labels
No labels
Activity
olix3001 commentedon Feb 21, 2026
task creation endpoint should be at POST /event/:event_id/task, and all task management should be handled directly through /task/:task_id, eventually task creation could be at POST /task while requiring event id as part of a payload
olix3001 commentedon Feb 21, 2026
we theoretically could use tstzrange which is built into postgres to guarantee chronology of start:end, but it might be hard to work with, so this decision is left for whoever decides to implement this task
olix3001 commentedon Feb 21, 2026
Task description is in markdown form, so it should be possible to handle arbitrary image upload for media used in the description. We could also validate markdown (for xss or sth)
Ask me if you need more explanation for the "media" part.