I'm working with an OpenAPI spec that is encountering errors where NJsonSchema determines if duplicate keys are present. In the spec, located here: https://developer.apiture.com/docs/apis/accounts/v0.67.0/openapi.json, there are two issues NJsonSchema encounters. The spec defines a schema named summaryExternalAccount. The schema includes a reference to another schema, abstractResource, which in turn includes a reference to yet another schema, abstractRequest, which defines a property called _embedded. Returning back to the summaryExternalAccountSchema, we find that this includes a further refined (but compatible) definition of _embedded. NJsonSchema does a nice job of pulling in the references, but fails to merge the compatible and identically-named _embedded properties. I'm having to hack in a fix for now, but it would be nice if we could fix this because other tools competing with NSwag are able to successfully process the OpenAPI spec.
Any chance this could get fixed? this is such a needed implementation. It makes no sense this PR has been opened for 4 years when a lot of people have been making posts regarding this issue
I'm working with an OpenAPI spec that is encountering errors where NJsonSchema determines if duplicate keys are present. In the spec, located here: https://developer.apiture.com/docs/apis/accounts/v0.67.0/openapi.json, there are two issues NJsonSchema encounters. The spec defines a schema named summaryExternalAccount. The schema includes a reference to another schema, abstractResource, which in turn includes a reference to yet another schema, abstractRequest, which defines a property called _embedded. Returning back to the summaryExternalAccountSchema, we find that this includes a further refined (but compatible) definition of _embedded. NJsonSchema does a nice job of pulling in the references, but fails to merge the compatible and identically-named _embedded properties. I'm having to hack in a fix for now, but it would be nice if we could fix this because other tools competing with NSwag are able to successfully process the OpenAPI spec.