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
Describe the bug
I am creating an OAS3 file from an existing API and one of the schemas includes a property named datetime which causes an Attribute exception when the generated model is imported.
To Reproduce
Steps to reproduce the behavior:
Convert a OAS3 file that contains a property named datatime:
Conversion succeeds with no errors or warnings
When executing generated code that has the offending model imported, an AttributeError will be thrown with message:
'Unset' object has no attribute 'datetime'
Expected behavior
A typed named datetime should be renamed with an underscore suffix like other built-in types
…e" [#557 & #558]. Thanks @kmray!
Co-authored-by: Dylan Anthony <[email protected]>
BREAKING CHANGE: `datetime` is now considered a reserved word anywhere, so any properties which were named `datetime` will now be named `datetime_`.
…e" [#557 & #558]. Thanks @kmray!
Co-authored-by: Dylan Anthony <[email protected]>
BREAKING CHANGE: `datetime` is now considered a reserved word anywhere, so any properties which were named `datetime` will now be named `datetime_`.
Describe the bug
I am creating an OAS3 file from an existing API and one of the schemas includes a property named
datetime
which causes an Attribute exception when the generated model is imported.To Reproduce
Steps to reproduce the behavior:
'Unset' object has no attribute 'datetime'
Expected behavior
A typed named
datetime
should be renamed with an underscore suffix like other built-in typesOpenAPI Spec File
Desktop (please complete the following information):
Additional context
This looks like a simple fix. I'll work on a PR.
The text was updated successfully, but these errors were encountered: