Skip to content

Queries with union type in upstream graphql service #3519

@DavideTriso

Description

@DavideTriso

Is your feature request related to a problem? Please describe.
Hello, I am currently evaluating Tailcall to merge multiple GraphQL services, along with some REST services, into a single unified GraphQL API.
One of the upstream GraphQL services I am integrating (a headless CMS) makes extensive use of unions. During testing, I observed that inline fragments in my queries appear to be removed before the request is forwarded to the upstream service.
I am unsure whether this behavior is expected, and my current schema requires additional configuration, or represents a current limitation of Tailcall.
Could you please clarify whether this is a limitation of Tailcall (and, if so, whether it is planned to be addressed in future releases), or if it might be due to a configuration issue?

Metadata

Metadata

Assignees

No one assigned

    Labels

    state: inactiveNo current action needed/possible; issue fixed, out of scope, or superseded.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions