List of OAS v3 issues addressed by this proposal

[darrelmiller]

• Support an operation to have multiple specifications per path (e.g. multiple POST operation per path) OpenAPI-Specification#182
  This is now supported by named request objects.

• Proposal: Multisegment Path Parameters OpenAPI-Specification#1459
  This is supported by the use of UriTemplates

• https://github.com/OAI/OpenAPI-Specification/issues/445

• Support interdependencies between query parameters OpenAPI-Specification#256
  These are supported by using a JSONSchema to define parameters

• '*' as a resource not possible, but defined for OPTIONS OpenAPI-Specification#2316
  This is supported by dropping the path leading slash requirement

[nebulon42]

Suggest to add OAI/OpenAPI-Specification#521.

[handrews]

I've added a "Moved to Moonwalk" label for issues that are only going to be addressed here (if at all). I am including issues that are clearly related to articulated Moonwalk proposals or principles, even if it is not clear whether that specific request will end up being handled.

This seems like it may be a little more manageable than keeping this list updated.