POST /projects , creates a project, but it's content is placed as the first task, not the project title | Voters

POST /projects , creates a project, but it's content is placed as the first task, not the project title

yolk

doing a

POST /projects

with body of

{
  "folderId": "REDACTED",
  "contentType": "text/markdown",
  "content": "910pm-20231022"
}

Will successfully create a new project, however it will be named "Untitled" with one task added with the

content

provided.

The response is HTTP: 200 with body:

{
  "ok": true,
  "item": {
    "id": "REDACTED"
  }
}

For more context, here's the

GET /projects/{projectId}/tasks

, which shows how the project's title is not filled in and the project has one task with the content provided in the previous request:

{
  "ok": true,
  "items": [
    {
      "id": "REDACTED_FIRST_TASK_ID",
      "text": ""
    },
    {
      "id": "REDACTED",
      "text": "910pm-20231022",
      "parentId": "REDACTED_FIRST_TASK_ID"
    }
  ]
}

Screenshot is the new project created.

October 23, 2023

pu239

According to POST /projects docs, You need a level 1 markdown heading in the content to make it the project title