widdershins
widdershins copied to clipboard
Mermade
OpenAPI / Swagger, AsyncAPI & Semoasa definitions to (re)Slate compatible markdown
**Is your feature request related to a problem? Please describe.** Unable to properly define response schema's especially in the context of multiple response content-types. **Describe the solution you'd like** The...
As per documented example and specification responses schema may include a `format` along with `type: 'string'`. In this case they're returning a PDF file with a `format: 'binary'`. https://swagger.io/docs/specification/describing-responses/ https://spec.openapis.org/oas/v3.0.3.html#schema-object...
**Description** When generating documentation for a schema that includes an object with a list of properties, and an "anyOf" or "oneOf", the example request given is invalid for the schema...
**Is your feature request related to a problem? Please describe.** I'd like a way to describe two request bodies to the same API path, but with somewhat different bodies. For...
When I run with max depth still some of the deep objects in examples come as '[objects]' instead of the actual object: Ex: ``` { "passengers": { "adult": [ {...
**Describe the bug** When yaml for an object contains both properties, and allOf. Only the properties show up in the generated markdown. (none of the allOf schema is included, except...
Hi All, Could someone point me in the right direction to remove the erroneous Scope Scope description Table headings that appear at the top of some of my markdown files?...
I am trying to include examples inside my responses using externalValue tag but it seems it is not supported currently. For e.g. "401": { "description": "Unauthorized.", "content": { "application/json": {...
Similar to how multiple *response* examples are [already supported in Widdershins](https://github.com/Mermade/widdershins/issues/111), it would great if it also support multiple **requestBody** examples. Here's an example yaml: ```yaml /foo: post: tags: -...
I'm currently using `widdershins` to convert an openapi-3.0 spec, into a slate/shin compatible markdown file. The cli throws the following error: ``` Invalid Variable Name "any+" in "{any+}" Error: Invalid...
