Overlay-Specification
Overlay-Specification copied to clipboard
OAI
The OAI Overlay Specification
I want to replace the value list of an array with a new list of values. However, the two overlay implementations I've tried treat the following example as "append to...
Sorry if this came up before, I searched but could not find anything. Environment variables have become something of the de facto mechanism to set server-specific values, then access them...
I'm proposing this change as a response to the ongoing discussion in #30 . Using "add" can be confusing and leaves us without being able to support some use cases,...
# A Canonical and Extended Forms for OpenAPI Specifications Following the discussion on last TSC and talking about [Traits](#613), [Overlays](#1722) and/or [Mixings](#1843), anyone can agreed these features are strongly oriented...
In a separate document. Has a separate lifecycle. How does the overlay reference the source document? - By document structure Is OperationId a valid way of referencing core documents?
#### Idea Sometimes you have some parameters you want to provide on every path. At the moment it is possible to reference them with the `$ref` tag. This works great...
## Scenarios [Emmanuel] Adding a big chunk of OpenAPI (e.g. adding a path) Adding beta methods Adding vertical specific annotations Is language translation a viable scenario for overlays? [Ron] Multiple...
Can a reference object (`$ref`) be used for the `update` property? update | Any | An object with the properties and values to be merged with the object(s) referenced by...
I would like to be able to add something like traits or mixins to operations. For instance, if I have a `GET /foo` that returns a list of foo objects...
