Skip to content

500 error when missing response object is missing type #653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alkalinecoffee opened this issue Sep 16, 2015 · 1 comment
Closed

500 error when missing response object is missing type #653

alkalinecoffee opened this issue Sep 16, 2015 · 1 comment

Comments

@alkalinecoffee
Copy link

When attempting to generate client docs via the swagger editor demo site, omitting the type from the schema of a response results in a 500 "something bad happened" error.

paths:
  /keys/current.json:
    get:
      summary: current key
      description: Returns info about the current key
      responses:
        200:
          description: json with information about the key
          schema:
            type: object <--- errors if this line is omitted
            properties:
              signing_key:
                properties:
                  name:
                    type: string

Swagger validation otherwise considers this valid.

@mohsen1
Copy link
Contributor

mohsen1 commented Sep 16, 2015

Yes, that's a know bug in swagger codegen. Please follow this: swagger-api/swagger-codegen#1170

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

No branches or pull requests

2 participants