Skip to content

Optional body parameters #3237

@lukaslihotzki

Description

@lukaslihotzki

There are 5 operations in data/api/client-server that don't require their body parameter (missing required: true):

Is this intentional? If yes, how can requests be made without body (for example, send null as application/json body)? And what is the effect of omitting the body? Except for searchUserDirectory, there aren't required parameters, so an empty body can be sent instead without obvious differences. About searchUserDirectory: Is search without search term supported by omitting the body completely? If so, why is the search term a required parameter of the body? postReceipt adds an extra field in the body, which would not work if the body is null.

I think this isn't intentional. Would you accept a PR that sets required: true in these bodies?

Metadata

Metadata

Assignees

No one assigned

    Labels

    aestheticA suggestion or issue relating to the representation of the spec

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions