I was facing an issue using and defining an interface in GraphQL when used together wi

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Interface resolver issues with Pydantic schemas about ariadne HOT 2 CLOSED

Verhaeg commented on July 22, 2024

Interface resolver issues with Pydantic schemas

from ariadne.

Comments (2)

DamianCzajkowski commented on July 22, 2024

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.

from ariadne.

DamianCzajkowski commented on July 22, 2024

@Verhaeg I suggest trying this approach, which omits resolvers. This code allows Pydantic to determine which metadata is returned. If you'd like, you can also try using ariadne-codegen.

from typing import List, Literal, Optional, Union

from pydantic import Field, BaseModel


class Search(BaseModel):
    search: "Response"


class Response(BaseModel):
    informations: Optional[List["Information"]]


class Information(BaseModel):
    metadata: Union[
        "Metadata",
        "MetadataBR",
    ] = Field(discriminator="typename__")


class Metadata(BaseModel):
    typename__: Literal["Metadata", "MetadataCommon"] = Field(alias="__typename")
    subject: Optional[str]
    date: Optional[str]


class MetadataBR(BaseModel):
    typename__: Literal["MetadataBR"] = Field(alias="__typename")
    subject: Optional[str]
    date: Optional[str]
    type: Optional[str]


Search.model_rebuild()
Response.model_rebuild()
Information.model_rebuild()

Example query:

query search {
  search {
    informations {
      metadata {
        subject
        date
        ... on MetadataBR {
          type
        }
      }
    }
  }
}

from ariadne.

Recommend Projects