Multiple ResponseSchemas

@ResponseSchema({200: SomeObject, 400: SomeErrorObject})
handler() { ... }

_Originally posted by @epiphone in https://github.com/epiphone/routing-controllers-openapi/pull/9#issuecomment-412455027_

Hi! Thanks for making this awesome library. I have a use case for multiple ResponseSchemas, what do you think of the mapping implementation as referenced in the above comment? If it sounds good I can work on implementing it.

[godwinpang]

opened up a PR @epiphone 😃

[epiphone]

So if I got it right (tests to verify this would be great) multiple ResponseSchemas work right now as long as each decorator uses a different statusCode or contentType. This is thanks to _.merge’s deep merging logic.

What doesn’t work is the case @thaigillespie described above, i.e., multiple ResponseSchemas for the same statusCode and contentType. oneOf seems like a good solution here indeed, probably implemented as part of the merging logic here: https://github.com/epiphone/routing-controllers-openapi/blob/81bfab558be469d058be1d048d4993072bb576df/src/decorators.ts#L58.

One downside of oneOf is that swagger-ui still can’t render it. I think other doc viewers like https://github.com/Redocly/redoc can though.