Mike Ralphson

Thanks. I think we would need to cope with more cases, but I like the method of preserving the pattern(s). Good idea!

The cases would be where `additionalProperties` already exists, as either a boolean or an object.

There are two Typescript parsers listed here https://github.com/Mermade/awesome-openapi3/blob/master/README.md#parsersmodelsvalidators

As a stopgap, you could always use the Mermade converter API as well as the validator API, to convert Swagger/OpenAPI v2 definitions to v3 before rendering...

Yes. If people have features of OpenAPI 3.1 they particularly want supporting as a priority, please list them here.

OpenAPI 3.1 GA has been released. You can track support for OAS 3.1 in the underlying library used by this project [here](https://github.com/Mermade/oas-kit/projects/1)

See PR #327 for a couple of proposed approaches.

See some history in #115 - I'll need to check if the PR for `externalValue` support in OAS-kit was ever submitted.

You could start by setting the `swagger2openapi` `refSiblings` option to `preserve` in `lib/openapi2.js` and see if that helps? I'm not sure which template you expect the sibling `description` to be...

OK, let me see about exposing that option for the next release.