Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for different response content types

See original GitHub issue

Swagger supports different content types in the response like this:

/health:
  get:
    responses:
      '200':
        description: Successful response
        content:
          text/plain:
            schema:
              type: string
              enum: ['UP','DOWN']

Currently it is not possible to define a response like this with fastify-swagger.

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:12 (11 by maintainers)

Top GitHub Comments

3reactions

mcollinacommented, Oct 20, 2018

Currently we don’t. I think we should enable this, but I’m not exactly seeing how. Would you mind to do a proposal? A PR would even be better.

We might even be lacking support for this in fastify itself.

Il giorno mer 17 ott 2018 alle 10:22 Gyula Szalai notifications@github.com ha scritto:

Swagger supports different content types in the response like this:

/health: get: responses: ‘200’: description: Successful response content: text/plain: schema: type: string enum: [‘UP’,‘DOWN’]

Currently it is not possible to define a response like this with fastify-swagger.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fastify/fastify-swagger/issues/117, or mute the thread https://github.com/notifications/unsubscribe-auth/AADL41g_ezDOCGdyy3eVon1ICna3R4Jkks5ulujYgaJpZM4XjYWt .

0reactions

climba03003commented, Feb 25, 2022