Create Model for Task-List

[WenInCode]

Problem

From the corresponding API issue

Currently, a project in code corps has many tasks. We need to create a new layer, 'task list', that allows ordered grouping of those tasks within a project. The task list should have the following properties:

• name: string
• position: integer
• tasks: has_many tasks
• project: belongs_to project

We'll also need to create/update mirage models & endpoints

Other model changes

Project:

• hasMany TaskLists

Tasks:

• belongsTo TaskList

Subtasks

• Create task-list model & mirage model
• Update project & tasks models & mirage models
• Create task-list mirage endpoint

References

• project model
• project mirage model
• task model
• task mirage model
• corresponding API issue

[WenInCode]

@joshsmith let me know if I am missing something, or maybe have something too much. I'll likely get started on this tonight, need to touch some other work up first.

[joshsmith]

@WenInCode would keep tasks on project still.

We also need to add position to task, I think.

[WenInCode]

@joshsmith sure. Mind if I ask why we should keep tasks on a project? I understand that tasks do belong to a project, but if they are on a taskList, would that not be enough? Just curious.

[joshsmith]

@WenInCode because we want to be able to do things in the future that don't require going through the intermediate relationship of the task list. The task list is a view into a project's tasks. But say I want to be able to do # autocompletion like GitHub. Or a search field for the tasks on a project. Maintaining that relationship lets us construct other such views into a project's task.