You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
Using a v3 spec for an object schema, when additionalProperties is True or unset or {} the type should be set for it
Looking at our generated models, the type is not set at the model level though it IS being set in CodegenProperty
The expected output is to have additional_properties_type = {str, int, float...} when it is incorrectly being set to additional_properties_type = None
This issue: #8813
Is also a blocker on getting this working because I need to define the vars that only the composed schema includes at the composed schema level.
Bug Report Checklist
Description
Using a v3 spec for an object schema, when additionalProperties is True or unset or {} the type should be set for it
Looking at our generated models, the type is not set at the model level though it IS being set in CodegenProperty
The expected output is to have
additional_properties_type = {str, int, float...}
when it is incorrectly being set toadditional_properties_type = None
This issue: #8813
Is also a blocker on getting this working because I need to define the vars that only the composed schema includes at the composed schema level.
openapi-generator version
5.0.0
OpenAPI declaration file content or url
Generation Details
openapi-generator generate -i issue_8743v3_wrong_response_type.yaml -o issue_8743v3 -g python
Steps to reproduce
Generate the client and look in both generated models. Both models lack the expected additionalProperties description.
Related issues/PRs
This came up when investigating #8743
Suggest a fix
The text was updated successfully, but these errors were encountered: