Ron

Currently, there's no way to control it, but why not just provide your own example that would be more meaningful?

@whitlockjc if I understand correctly, this is the `example` field from the schema definition itself, not the `examples` field in the Response Object. I think it's ok to use it...

Unfortunately, for 2.0, this is valid.

spec-wise, the client would be expected to send the content type header as application/json. However, when it comes to validation, I'm fairly indifferent to this case. Seems like a reasonable...

I'm guessing TL;DR won't work here? :blush: Let me have a look.

Okay, I hope I got everything needed from the thread. If the intention is to pass `Command` as a (body) parameter, and `Command` has a `discriminator`, then indeed anything that...

@whitlockjc - that is correct and the explanation @daveismith provided is fairly accurate. The `discriminator` is used to declare inheritance between models (unlike the simple usage of `allOf` that's basically...

When I was talking about recursion, there are two cases: - There's a model (ModelX) with `allOf` parent that doesn't specify the `discriminator` value (composition), and then there are models...

`default` is not an error. It's a general-purpose response which can be used as an error or not. There's no real need to mark responses as error. By standard, 2XX...

I'll mark is as a proposal for the next version and we'll see how people respond to the suggestion.