Skip to content

all response fields are optional #16

@mattfysh

Description

@mattfysh

hi @anbraten thanks for this client lib! i noticed all fields in responses are optional:

Image

is this intended? I understand this library is generated from gitea's swagger spec, is this how their spec is coded, or is there an issue in the autogeneration?

making every field optional is making it difficult when the types are used elsewhere in the app, resulting in a lot of string | undefined types throwing errors for places that accept just string

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions