Closed botchniaque closed 8 years ago
Thank you for your feedback! It looks like this is an issue with swagger-rb
, the underlying library swagger-diff
uses to parse Swagger specifications. Unfortunately, we’re juggling a few different priorities at this time, and probably won’t get to this quickly. If you’re interested, we’d welcome a PR addressing this issue. It looks like there are a few possible ways to approach this:
swagger-rb
and wait for them to fix it. However, swagger-rb
appears to be inactive, or possibly abandoned, so I don’t anticipate any issue being addressed quickly.ruby_swagger
looked to be a viable candidate that was under active development, though it's also pretty young, so may not be feature-complete yet. swagger_parser
was another candidate. It was less active, though also had no outstanding issues/PRs, so may just be stable. If you wanted to attempt replacing the Swagger parser, it would be worth investigating the current state of parsers, in case someone released a better candidate since I last looked.If you opt for 2 or 3, you may also want to file an issue with swagger-rb
so they’re aware and can address the underlying problem if and when they have time.
Either way, we’d be happy to review a PR, and appreciate the contribution!
Sorry for no reaction on that. Sadly I will not be able to pick that, as I'm also flooded with work.
I just released Swagger::Diff 1.1.0. Among other improvements, it replaces the underlying parser, and should now support your Swagger specification. If you encounter any other problems, please let us know.
I use parameter references in my swagger specs, and the diff fails because it expects parameter to have
name
attribute provided.As of Swagger Specs, parameter may contain a reference object, and reference object does not have
name
attribute.My
param-ref.yaml
fileWhen I call
swagger-tools param-ref.yaml param-ref.yaml
(same file just for simplicity) I get the below error.