Henry Andrews

PR merged for 3.0.4 and ported to 3.1.1 via PR #3921!

Hmm... this one is complicated because it's three separate tables of fixed fields: the general fields, and the each of the two mutually exclusive options. It's not _just_ that exactly...

Ah, I was actually wrong about part of it, `example` and `examples` only go with `schema` because they can be specified differently in `content`. It's actually not clear to me...

PRs for all active lines merged! Closing.

This was a 2.0 question and the question to the OP in 2017 has been unanswered. I'm going to close this - please feel free to open a new issue...

With `simple`, the "n/a" for empty doesn't make sense as it's part of RFC6570 that undefined values are just not serialized for `simple`, so we should indicate that. I'm inclined...

@OAI/tsc review request: Am I missing anything with the n/a's?

@silkentrance I've expanded PR #3859 (which already addressed the "rendering" part of this) with the remaining fixes. I went with _n/a_ in italics to keep from making the table any...

PR merged for 3.0.4 and ported to 3.1.1 via PR #3921! _n/a_ was kept where described in the previous comment. We ended up changing the "empty" comment to "undefined" and...

`style: form` with a string, number, boolean, or null just puts the value directly as the parameter value- there is no need to do anything more complicated, which is why...