James Messinger

@matjung - As @jdegre pointed out, the reason you're getting an error is that the server (`www.micro-work.net`) does not have CORS configured to allow remote requests. You'll need to talk...

Thanks for reporting this. And especially for providing a full code sample! 🙏 I'll add it to the test suite so we can determine the cause

What would you propose as a solution? Keep in mind that `a` and `b` _aren't_ the same object. They both simply get _some_ of their properties from the same object.

Swagger 2.0 and OpenAPI 3.0 don't allow `$ref` to be used on the same object as other properties. So this is invalid: ```yaml in: query name: bar required: false $ref:...

Good point. I was thinking in terms of the `dereference` method, not the `validate` method. I agree that for `validate` (and _maybe_ `dereference` too) it makes sense to default to...

There's a subtle difference between bundling and stitching. This CLI currently only provides the former, not the latter. Bundling is simply a matter of resolve `$ref` pointers and inlining whatever...

The OpenAPI spec builds off a few other specs, namely [JSON Schema](https://tools.ietf.org/html/draft-wright-json-schema-00), [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03), and [JSON Pointer](https://tools.ietf.org/html/rfc6901). The `$ref` properties in an OpenAPI document are JSON References, and the _values_...

That output comes from the [JSON Schema validator](https://github.com/zaggino/z-schema) that I'm using. And, agreed, it's not always very intuitive. I'm currently working on a new version of Swagger Parser that will...

Circular references are fully supported. Please see [the docs](https://github.com/BigstickCarpet/json-schema-ref-parser/tree/master/docs#circular-refs) for more information. The error message that you mentioned above does **not** appear to be due to a circular reference though....

Ok, cool. I was able to reproduce the problem. Looks like a bug in [Swagger-Parser](https://github.com/BigstickCarpet/swagger-parser). In the meantime, here's a workaround that I found: **swagger.yml** ```yaml swagger: "2.0" info: title:...