☂️ Umbrella Issue: Threads

[inyono]

Status

• [x] Queries are done 🎉
• [ ] Mutations are tracked here: #111 and #177

---

We want to add threads to the uuid type. So no additional root query necessary. Something like:

{
  uuid(id: 1855) {
    threads {
      totalCount
      nodes {
        id
        createdAt
        updatedAt
        title
        archived
        trashed
        object # Back link to the uuid the thread is tied to
        comments {
          totalCount
          nodes {
            id
            content
            createdAt
            updatedAt
            author
          }
        }
      }
    }
  }
}

Furthermore, we need mutations for various types of actions:

mutation createThread(
  # ...
}
# createComment
# archiveThread
# ...

Required legacy API endpoints

• GET /api/threads/:object-id returns all the threads for the object with the given id (with thread ids only)
• GET /api/thread/:id returns the thread with the given id (including its comments)
• POST /api/create-thread creates a thread
• ...

[inyono]

@anbestCL: There are now helpers to handle the connection stuff (i.e. returning totalCount, nodes, edges etc.). See https://github.com/serlo/api.serlo.org/blob/master/src/graphql/schema/notification/resolvers.ts#L64 for a usage example.

[inyono]

There's a work-in-progress PR https://github.com/serlo/api.serlo.org/pull/24 that might help.

[kulla]

@inyono Comments do only have a date field since they cannot be edited currently. Are the fields createdAt and updatedAt already for the future comment system?

[inyono]

createdAt and updatedAt are the fields we want to have in the long-term. Since we don't want the API to change later, we should already implement those (by setting both to the existing date field).