Skip to content

Enhancement: Combine planner task get with planner task details get  #3257

@Jwaegebaert

Description

@Jwaegebaert

If we take a look at the command planner task set we can see here that when it is executed we will get a response that is a combination of the model PlannerTask and PlannerTaskDetails. We want to make this uniform to the other planner task commands.

Here we will start with combining the commands planner task get and planner task details get into a single command planner task get. When we look at both output models for these commands, there will be one property we have to watch out for.

planner task get > PlannerTask Model:

{
  "createdBy": { },
  "planId": "xqQg5FS2LkCp935s-FIFm2QAFkHM",
  "bucketId": "gcrYAaAkgU2EQUvpkNNXLGQAGTtu",
  "title": "title-value",
  "orderHint": "9223370609546166567W",
  "assigneePriority": "90057581\"",
  "createdDateTime": "2015-03-25T18:36:49.2407981Z",
  "assignments": { },
  "id": "01gzSlKkIUSUl6DF_EilrmQAKDhh"
}

planner task details get > PlannerTaskDetails Model:

{
  "description": "Task details properties:\nchecklist:Sub items\nreferences:Related links",
  "previewType": "automatic",
  "references": { },
  "checklist": { },
  "id": "01gzSlKkIUSUl6DF_EilrmQAKDhh"
}

So here I've simplified a few parts but you' ll see here that both models do return the same Id. This is in both cases just the task Id. With combining the two models we will need to check that we don't return the Id twice.

More info can be found here #3231

Note: Let's start by putting this issue on hold until #3229 comes throught. I'll kick it up a notch to get this one done. 😄

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions