Helen Kosova

Here's a spec with `x`-extensions everywhere where possible: https://gist.githubusercontent.com/hkosova/5e7cefb487efd4001a97ff3c2fb20716/raw/d15880709f672f14b5e01ca5135f181a60eea6e6/extensions.yaml Currently the converter removes `x-` extensions from: - root level - under `paths` - individual operations - `items` in array parameters...

Another spec to test how extensions are converted: https://gist.github.com/alasdairhurst/a1073a85d3df4bc800e143a4d31dd168

This seems mostly fixed except the extensions inside: `info.contact` `paths` `responses` - possibly caused by https://github.com/swagger-api/swagger-parser/issues/719 `responses.` Schema.`xml` Array.`items`

@braindeaf make sure you have `security` requirements defined for operations or on the root level, e.g.: ```yaml security: - apiKey1: [] apiKey2: [] ``` If this doesn't help, [open a...

> make the "Responses" section more visually different from the actual response This is discussed in #6548

> However, there doesnt seem to be a way to set additionalProperties = true on the just the object? FYI, `additionalProperties: true` is the default value for objects. That is,...

Related: [Vary presence and requirement of properties with CRUD operation](https://github.com/OAI/OpenAPI-Specification/issues/1497)

@alequetzalli > I feel like I just saw someone else do this same PR... It was me! :sweat_smile: This is a new version of my PR #957 from a few...

The correct syntax is ```yaml variables: ver: default: '100' ``` In any case, the editor should handle this more gracefully rather than crash. The problem is also that the spec...

@tim-lai or it could be an issue with the `allOf`/`$ref` resolver. I updated the description with additional observations.