Chris Smith

If you define the `second` property as follows (with the `$ref` within an `items` member), then you get the result you expect (for `second`). ```javascript "second": { "type": "object", "description":...

The problem seems to stem from `go-openapi`, the specification parser used by DapperDox. Without the `"items":{}` wrapper around `"$ref": ...` we do not get a `Description` returned by `go-openapi`. I've...

We've got the answer. JSON schema states that other properties in an object with $ref need to be ignored. http://json-schema.org/latest/json-schema-core.html#rfc.section.7 So what `go-openapi` and thus DapperDox is doing is correct....

Still working on this. It's a little complicated!

Yes definitely - we're downstream of go-openapi parser, which handles spec parsing for us. And internally we're spec neutral (ish), so short answer: yes!

Just waiting on go-openapi