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
I was facing an issue using and defining an interface in GraphQL when used together with Pydantic. The solution I finally managed to wotk with will not scale very well (not elegantly nor pythonic IMO).
PS: using latest versions of Flask (3.0.3), Pydantic (2.7.1) and Ariadne (0.23.0).
interface_metadata=InterfaceType("Metadata")
@interface_metadata.type_resolverdefresolve_metadata_type(obj, *_):
ifisinstance(obj, schemas.MetadataBR):
return'MetadataBR'return'MetadataCommon'# Returning the base value just for testing, could be None
In my code, currently I generate only MetadataBR. But with the current definition of the Information model for Pydantic (where I define metadata being any class that can be evaluated to a base class and I can increase the number of possible classes in the future without adding new possible combinations to this field using Union). When the code reaches the resolver function, obj for some reason comes with type schemas.Metadata and without the type field that is setted in the code.
Somewhere inside Ariadne code, it is converting my code to another type because if in my resolver, after I fetch the information and before returning the values, I try to dump the types and values, they all come correctly (MetadataBR and with type field).
What I had to do to make it work was change my python model to:
Thanks for pointing this out. I'll take a look at it soon and let you know if it's a bug or if there's something that can be adjusted in the code. I'll get back to you as soon as I can.
I was facing an issue using and defining an interface in GraphQL when used together with Pydantic. The solution I finally managed to wotk with will not scale very well (not elegantly nor pythonic IMO).
PS: using latest versions of Flask (3.0.3), Pydantic (2.7.1) and Ariadne (0.23.0).
The basic GraphQL:
Basic Pydantic schemas:
The interface resolver:
In my code, currently I generate only
MetadataBR
. But with the current definition of the Information model for Pydantic (where I define metadata being any class that can be evaluated to a base class and I can increase the number of possible classes in the future without adding new possible combinations to this field using Union). When the code reaches the resolver function,obj
for some reason comes with typeschemas.Metadata
and without thetype
field that is setted in the code.Somewhere inside Ariadne code, it is converting my code to another type because if in my resolver, after I fetch the information and before returning the values, I try to dump the types and values, they all come correctly (MetadataBR and with type field).
What I had to do to make it work was change my python model to:
If I increase the number of metadata sub models, I would need to keep adding to several Unions.. making it not so readable.
Not sure if I missed something, but would be nice to have that working.
Thanks
The text was updated successfully, but these errors were encountered: