David Denton

Nice idea - might be worth investigating if we can get most of the lower level security stuff for free. When you say `Security` do you mean an auth0 class?

The tasks that have been removed are used as a part of our build process to check compatibility against the open api generator, so can't be removed I'm afraid.

To enable a "oneOf" type functionality in the docs you can just register "returning" with each variant in turn.

See: `OpenApi3AutoTest.renders as expected.approved` to see this tested

Ah - sorry. There might be a way to implement this with some type of annotation (on the field) which then gets picked up and processed by the renderer. But...

As an update, we now have the ability to discriminate between multiple examples by providing a "prefix". This is limited in that it adds this prefix to all objects created...

We hadn't come across that issue - PR would be great.

This is because multipart Response aren't supported at the moment. Will rename and keep this issue open to track, but TBH it's not going to be something that gets looked...

I don’t see the hack as a viable forward option at all. I also know that the current implementation of multipart form data is pretty complicated. At the very least...

Feel free to PR it! It will be interesting to see if Ktor websockets fit into how we have modelled them! 😄