Mike Raineri

I reached out to some OData folks to help clarify; what you're doing is perfectly legal, and we will need to adjust the tool to allow for it.

Currently we don't have a way of doing this, and it's been something that's been on my mind too. Unfortunately I haven't thought of a clean solution for this.

The schemas we publish should follow OpenAPI 3.0.1. I've had limited success so far with code generators with OpenAPI 3.0. At least looking at go-swagger, it appears it's still on...

Excellent work @joelrebel ! I have a fix in the tool ready for what you did; it was brought up in issue #169 and will be ready for the next...

An update from recent testing: working with 2019.2 and the latest version of Swagger Codegen, everything seems to work successfully, with one minor exception. When generating Python code, it will...

Unfortunately OpenAPI doesn't support the "patternProperties" concept that JSON Schema has. There were some discussions about it a while ago, but I don't think anyone on the OpenAPI front is...

Thanks for the info; I'll see if we really need to update our JSON Schema files to support 2020-12; if there's enough backwards compatibility, we might be able to keep...

At this time, this is not in scope for what we have for tools. There are OpenAPI tools where you should be able to point them at your service's OpenAPI...

Unfortunately that's a private repository only accessible to members of the organization. We shouldn't have any examples in here that reference it. We'll need to clean this up to decouple...

Moved to Redfish-Tools since this is the repo that contains the JSON Schema to OpenAPI converter.