Skip to content

support indicating "required" values #5

@petri

Description

@petri

When an API is wrapped, it can be useful to be able to provide a list of variables that the user or higher-level app should provide at minimum for the call to work. Sort of "required" values that the API spec itself cannot itself provide.

There could be one common required key or one for params and one for the body. Perhaps one common setting would suffice though.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions