openapi-preprocessor
openapi-preprocessor copied to clipboard
dolmen-go
An authoring tool for OpenAPI specifications
I've been able to merge `paths` in from multiple files, but we haven't been able to figure out how to split the requests, responses, and schemas into separate schemas. I've...
Hey @dolmen, I noticed an issue with my doc after running preprocessing. I have the following config in yml: ``` security: - httpBasic: [] .... components: securitySchemes: httpBasic: type: http...
Currently `securitySchemes` are deleted because there are no `$ref` pointers to them. That's intended since that's how they work. Solves #10
Thanks for creating this tool, it looks really useful. It would be great to have an option that doesn't dereference `$ref`s. There are some references, like ones that point to...
If I create a YAML object named "components" in my `input.yaml` file, any `$ref`, `$inline` or `$merge` commands don't resolve. It works fine if I name it "component" though. Example...
The restriction on where **$ref**'d content is inserted means that common examples of **$ref** usage cannot be used with this preprocessor. That means an existing project really can't adopt the...
About YAML 1.2 anchor & aliases: http://www.yaml.org/spec/1.2/spec.html#id2765878 This YAML specific feature could be used instead of `$merge` or `$inline` for some uses cases. We should document the similarities and differences.
The error of this line is not printed in the output making it hard to understand what failed. Can you please add it? https://github.com/dolmen-go/openapi-preprocessor/blob/33bcf818670f21e1ac9ba15c2d9d4859dca37b6e/refs.go#L656
