Skip to content

Response schema marked as "Optional" #247

@Krismix1

Description

@Krismix1

The response schema is marked as "Optional" but I don't think there is a way to mark it as required in the specification data (docs about describing responses in OA3).
image

Version: 0.6.4
Commit: 0beb11b
Reproduction spec:

openapi: 3.0.0
servers: []
info:
  description: |
    Example
  version: 1.0.0
  title: Swagger Petstore YAML
tags:
  - name: pet
    description: Everything about your Pets
paths:
  /pet:
    post:
      tags:
        - pet
      summary: Add a new pet to the store
      description: Add new pet to the store inventory.
      operationId: addPet
      responses:
        "200":
          description: successful operation
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Pet"
        "405":
          description: Invalid input
      requestBody:
        $ref: "#/components/requestBodies/Pet"
components:
  schemas:
    Pet:
      type: object
      required:
        - age
      properties:
        age:
          description: The age of the pet
          type: number
          example: 5
  requestBodies:
    Pet:
      content:
        application/json:
          schema:
            allOf:
              - description: My Pet
                title: Pettie
              - $ref: "#/components/schemas/Pet"
      description: Pet object that needs to be added to the store
      required: true

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions