openapi-format
openapi-format copied to clipboard
thim81
Format an OpenAPI document by ordering, formatting and filtering fields.
Hi! I tries to use this package to downgrade a 3.1 spec file to a 3.0 one. That result in success, but the file is still in 3.1. I doing...
Hi, I am trying to filter a yaml openapi spec, to remove a path and remove unused schema components. The path filtering works fine, but the unused component removal does...
Hello Tim, I'm using your wonderfull tool to extract few interfaces from a big openapi file using inverseTags and unusedComponents filter. Unfortunately it looks like there are some used objects...
And if possible, please publish the d.ts file to [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped).
Currently it is not possible to sort properties, schemas or responses by name, because any order defined for them is applied to the nested objects instead. In order to distinguish...
I couldn't figure out how to do this. I need the get, post etc. request parameters to be ordered by the value of the `name` field. The parameter fields themselves...
My goal is to create normalised openapi.json files which developers can confidently review in a PR before deploying to apigee. This tool seems promising in helping us achieve that. Unfortunately...
Hi, first of all, thanks for your tool that helps keeping API definitions and commits clean. ❤️ `prettier` has a [CLI](https://prettier.io/docs/en/cli.html) that makes it really easy to use it in...
Currently, openapi-format dereferences the OpenAPI documents to do its formatting, sorting, ... and write a dereferenced result. Investigate the option to leverage: https://www.npmjs.com/package/json-refs to format the OpenAPI documents and update...
I have no idea if this is intentional, or just a difficult problem to solve, but comments are stripped from YAML OpenAPI specs. This becomes a little bit problematic when...
