Skip to content

Client response data types differ from API docs #30

Description

@sreuter

According to the official REST API docs, some fields like slug and id are guaranteed to be there. When looking at the of the client, these fields are marked as optional, e.g. can be undefined. That makes using the client unnecessarily complicated, as either explicit checks for availability of those fields need to be added to the code, or fields need to be declared as explicitly available, e.g. data.slug! when being used.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions