Swagger 2: Components Response `required: true` is not valid swagger

[simonireilly]

Description

Path parameters are singleton resources, and have the schema of required: true to specify their _require_ment

paths:
  /users/{userId}:
    get:
      summary: Get a user by ID
      parameters:
        - in: path
          name: userId
          schema:
            type: integer
          required: true
          description: Numeric ID of the user to get

Schema response components and request bodies use the required: [] syntax to specify which of the fields in their object structure must be provided.

Assertion

The popular redocly CLI replaced the depreacted swagger cli and can be used to lint the produced swagger 2.

npx @redocly/cli lint doc/apidoc/schema_swagger_json.json 

Benefit

Once there are far fewer errors generated in the swagger 2 file, the errors which are important for user action will be far easier to see, and act upon.

Fix

When generating swagger from ApiPie remove the required: true generated output from the JSON for request bodies and response bodies, but preserve the array definition

[mathieujobin]

Thank you for opening this well described issue.

Can you open a Pull request with the necessary changes?

[jaynetics]

it seems to be as easy as removing this line, but i'm a bit unsure what is right here because the official json schema of 2.0 says a boolean is valid...

[justinperkins]

Isn't the required: true format valid OAS3?

[mathieujobin]

maybe we need to have a v2 and v3 output with some differences... anyone volunteer to do that work ?