Closed coandco closed 1 month ago
There are a few peculiar things about this document, none of which we’re likely to have an easy solution to:
oneOf
. I’d need to read some of the jsonschema spec to see if that’s even allowed, and if so how to resolve it.So no obvious way to support this schema in this project. Maybe take a look at the openapitools generator and see what they do with it?
Gonna close this since I don’t think it’s a bug.
Describe the bug I'm attempting to use openapi-python-client to generate a client for the new XPipe API, but it's failing with "Cannot take allOf a non-object". I've boiled it down to the following minimal reproducer. I think what the original spec is trying to describe is an auth type that always has the key "type", and then either has one key or the other based on what type it is.
OpenAPI Spec File
Desktop (please complete the following information):
Additional context I'm fairly new to openapi specs, so it's entirely possible I'm misreading the file or that the original spec is doing something hinky that I don't understand. What am I missing here?