When running openapi-python-client generate with both the standard and dereferenced openapi.yaml files, multiple errors are raised that prevent a full client spec. Removing reference errors drops the count from 37 to 6 (half of which only affect the staff/ endpoint), which is manageable and I can address it downstream, but I wanted to make sure I'm not missing something.
The 6 errors in the deref are bucketed into 4 categories:
- Unsupported content type on
/users/custom_style.css (looks like the CSS file got added by mistake?)
- Unsupported content type
multipart/x-www-form-urlencoded (which appears to be a portmanteau of application/x-www-form-urlencoded and multipart/form-data as per MDN)
- Conflicting enums for
CommentVote
- Duplicate models
VoteTrendType2Uploader
The rest of the errors from the referenced version are Could not find reference in parsed models or enums or some variation on Invalid property in union response_200. I've attached the error logs as reference.
errs.log
deref.errs.log
When running
openapi-python-client generatewith both the standard and dereferenced openapi.yaml files, multiple errors are raised that prevent a full client spec. Removing reference errors drops the count from 37 to 6 (half of which only affect thestaff/endpoint), which is manageable and I can address it downstream, but I wanted to make sure I'm not missing something.The 6 errors in the deref are bucketed into 4 categories:
/users/custom_style.css(looks like the CSS file got added by mistake?)multipart/x-www-form-urlencoded(which appears to be a portmanteau ofapplication/x-www-form-urlencodedandmultipart/form-dataas per MDN)CommentVoteVoteTrendType2UploaderThe rest of the errors from the referenced version are
Could not find reference in parsed models or enumsor some variation onInvalid property in union response_200. I've attached the error logs as reference.errs.log
deref.errs.log