Open kyle-kc opened 1 month ago
Yes, it works like that by default. I think that this need fix
Thank for your feedback about this feature! I haven't tested it much.
I understood why it was done this way.
Because Union[ClassA]
it is defined as a type ClassA
.
See https://docs.python.org/3/library/typing.html#typing.Union
Describe the bug When using a singular union type with
graphql_fields
(i.e. a field with a union type with only one sub-type within the union), the field is rendered only with the fields within the singular type, not using an... on
statement for composite types. This breaks if you're querying a composite type but only want one potential return type.To Reproduce Steps to reproduce the behavior: Create the following classes:
Then call
ClassB.graphql_fields()
. This renders as:Expected behavior It should render as