Henry Andrews

PRs merged – closing!

I could see two approaches here: 1. Special-case `*` as a "Path Template" 2. Allow defining an Operation Object on a Server Object I lean more towards the special-case, as...

Hmm... although now that I think of it, is `*` really better associated with deployments since it is server-wide? 🤔 The only reason to describe `OPTIONS *` is to describe...

@OAI/tsc review request: Is it worth figuring out where to put support for `OPTIONS *`, either in 3.2 or later in 3.x? If so, should this go with Paths (shape)...

@ralfhandl Darrel's comment is a reason not to handle it in the Paths Object, but it could be handled in the Servers Object. @mikekistler we decided recently that minor releases...

@ralfhandl if we're postponing this based on modelng HTTP, then we should close this as "Moved to Moonwalk" (as we have everything else that is being addressed there, even if...

@karenetheridge the multiple files with the same name is [handled with a property that is itself an array](https://spec.openapis.org/oas/v3.1.0#considerations-for-file-uploads) (see example at the end of the linked section). It's on my...

It looks like `prefixItems` won't help with `multipart/mixed` because the Encoding Object applies to every item in the array, which works fine with the single-schema `items` syntax that was the...

@jeremyfiel @karenetheridge OK I've been thinking on this more, and I realized that my statement that `multipart/mixed` uses the `attachment` dispositions is incorrect. The `multipart/mixed` RFC is [§5.1.3 of RFC2046](https://www.rfc-editor.org/rfc/rfc2046.html#section-5.1.3)...

@ggirodda I think you can just do ```YAML ... responses: '200': $ref: '../index.yaml#/components/responses/200Ok' ``` `allOf` is a schema keyword and is only allowed in schemas. Usually it's the schema that...