Repository navigation
Allow boolean values in enum #785
Description
Describe the bug
Error(s) encountered while generating, client was not created
Failed to parse OpenAPI document
4 validation errors for OpenAPI
components -> schemas -> ErrorResponse -> $ref
field required (type=value_error.missing)
components -> schemas -> ErrorResponse -> properties -> error -> $ref
field required (type=value_error.missing)
components -> schemas -> ErrorResponse -> properties -> error -> enum -> 0
value is not a valid integer (type=type_error.integer)
components -> schemas -> ErrorResponse -> properties -> error -> enum -> 0
str type expected (type=type_error.str)
To Reproduce
Steps to reproduce the behavior:
openapi-python-client generate --url https://topaz.grv.org.au/docs/swagger.json
Expected behavior
API Client generation.
OpenAPI Spec File
A link to your openapi.json which produces this issue.
I tried converting this to OpenAPI3.0 with the same issue.
Desktop (please complete the following information):
- OS: Windows 11
- Python Version: 3.11
- openapi-python-client version 0.15.0
Additional context
Is this an issue with the spec file?
Activity
dbanty commentedon Aug 12, 2023
Looks like the thing it's mad about is using
enumwithbooleanforErrorResponse—only string and integer enums are supported right now. You could get this spec working for now, as a workaround, by removingenum: [true]from that section.I'll convert this issue into a request to support booleans in enums as is allowed by json schema
[-]Error(s) encountered while generating, client was not created[/-][+]Allow boolean values in enum[/+]