yolk
Would like to have a
PUT /{taskId}/content
(or eventually a
PATCH /{taskId}/
) route be available for updating atomically the task content.
I understand there's a
PUT
pattern now for
DATE
s and
ASSIGNEES
, I think that would be fine pattern to adopting too, with a
PUT /projects/{projectId}/tasks/{taskId}/content
to update the
content
directly.
To expand on mentioning
PATCH
routes, I think a
PATCH
would work at the root path of
/projects/{projectId}/tasks/{taskId}/
, without any path indicating what we're updating on the task in the body (
content
,
assignee
,
[attachments]
...), and using what I see the API has now as the pattern going forward.
I see the pattern as
  • "PUT == create or update a /{piece} of item"
    (uses selection of
    item
    at
    .../collection/item/piece/
    )
  • POST == create the whole item
    (uses root of
    item
    at
    .../collection/item/
    )
  • PATCH == update a part of the already-created item
    (uses root of
    item
    at
    .../collection/item/
    )