You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I vote against using x- extensions. that renders them generally unusable by OpenAPI tools.
I would like to see each example be an Example Object with at least a description, as may examples require or benefit from at least some explanation.
I like the freedom of either singular exampleorexamples but not both (i.e. oneOf). It's a simple transformation from singular to list in tools. We should support the examples array. Most cases probably have only one example, but we should not make it more cumbersome the majority by requiring examples: [ ... ]
In the definition of a Content Type Object we currently allow either an array of 'examples' or a single 'example' object.
There are conflicting opinions on how we should do this:
example
object and allow secondary examples to be defined using x- extensionsexamples
array and require a single item array for single examplesexample
andexamples
The text was updated successfully, but these errors were encountered: