Description
Describe the bug
My understanding of allOf is that its supposed to recursively combine 2+ dictionaries and only fail if multiple types cant be satisfied(such as if the same path has different types assigned). At first I thought it didn't like it if subdictionaries had different values but then I realized other openapi tools validated it and it didn't have conflicts.
I managed to cut down the example and even having the same two subdicts with the same name triggers the error
Cannot parse response for status code 200 (Properties has conflicting values), response will be omitted from generated client
openapi-example.yaml.json because github doesnt like yaml
rename to yaml and run openapi-python-client generate --path openapi-example to verify.
https://editor.swagger.io/ validates it and will even let you generate official swagger client with this example
OpenAPI Spec File
A link to an OpenAPI document which produces this issue. Ideally, write a minimal reproduction only containing the problematic pieces.
Additional context
result
Generating example-client
Warning(s) encountered while generating. Client was generated, but some pieces may be missing
WARNING parsing GET /test within default.
Cannot parse response for status code 200 (Properties has conflicting values), response will be ommitted from generated client
Also apparently ommitted is a misspelling and it should be omitted