YAML spec is correctly parsed with --input-file-type jsonschema
I have a YAML spec, for which datamodel-codegen was working fine until the release 0.18.0.
With 0.18.0 I see some unexpected code generation when I do not specify any --input-file-type and when I specify --input-file-type yaml.
I only get it to work (same code generated as before) if I specify --input-file-type jsonschema. But my input spec file is YAML and swagger 2.0, not jsonschema.
I can provide a sample yaml spec to reproduce this if needed.
But I first wanted to make sure this is not an obvious bug.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too