As a user I can add a list of things to be done within a task so that I can track the goals to be met or use the feature as a shopping list about tracke.rs HOT 3 CLOSED

Some remarks after taking look at those criteria after some time since those were written:

• The first item on the list qualifies rather as implementation detail and probably shouldn't be here
• That first point is rather problematic: there is no reason to have a separate table for the list if there will ever be only one for each task. The list can be implemented as an array in PostgreSQL.
• PUT updates with changed index number should in such situation error with status 409 ("Conflict"). - this constraint simply makes a poor user experience and it shouldn't be here.

The first point is the most unfortunate in my opinion - as far as the API ergonomics go having an id mapping to a list which is in 1-to-1 relation with the task anyway makes no sense, querying the lists table through a join is less efficient and implementation is not even simpler this way. Because of that I will start with ignoring that criteria.

from tracke.rs.

Alright, now I remember what the list id was for - the list items need a boolean field marking whether it is completed or not and while it is supposedly possible to make diesel work with PostgreSQL composite types (according to this issue, nvm, I do not want a link here, it would lead people looking for more info on that in here for nothing) we have no performance requirements (as part of the WAT2023 project) and so it is not worth the work at the moment. It will be easier to make task and list items have 1-to-many mapping with list table working as join table.

from tracke.rs.

So finally it ended up being the array of composite types - implemented in commit closing the issue #56

from tracke.rs.