Skip to content

Expand types of lists that can be returned in responses #93

Closed

Activity

  1. ghost changed the title [-]$ref is optional and should not be mandatory for items[/-] [+]$ref should be optional for items[/+] on Jul 15, 2020
  2. dbanty commented on Jul 15, 2020

    @dbanty
    Collaborator

    Our response types in general are pretty basic compared to our "properties" (inputs). The right move here is probably to unify those two types, maybe by having a generic response with a single root Property that makes it up.

    I need to do some research into what's allowed first though. I'm not sure if you actually can return all the same things you can take as inputs (or if the schema is defined the same).

    If you (or anyone else) knows off hand or wants to do some reading in the docs to find out, that would go a long way toward moving this forward.

  3. changed the title [-]$ref should be optional for items[/-] [+]Expand types of lists that can be returned in responses[/+] on Jul 15, 2020
  4. added this to the 0.7.0 milestone on Aug 18, 2020
  5. dbanty commented on Sep 26, 2020

    @dbanty
    Collaborator

    #165 actually added a bunch of additional list types so I think that solves this particular issue. I do still plan on expanding the available response types, but it will be done against some other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions