Code Monkey home page Code Monkey logo

Comments (3)

Yogu avatar Yogu commented on July 28, 2024

You are correct, root types are merged. However, if you specify a namespace, its root types are wrapped in a field on the newly generated root type first - thus, you have two query types:

# newly generated query type
type Query {
  demo: Query # referencing the original Query type of demo
}

# the original Query type of demo
type Query {
  // original fields of demo's Query type
}

This generates the error about duplicate types you got. You should use typePrefix in conjunction with namespaces to avoid these kind of conflicts. I could also see an extension to graphql-weaver that allows to specify the names of the newly generated root types, so you could disambiguate the two types - but this would fail with the next endpoint as it probably also has a Query type. Or you could just rename the Query type in the referenced schema if it is controlled by you.

If I add typePrefix, schema becomes strange:

Query → demo → Demo__Query → ...  stuff

While queries perform correctly, I don't understand, why this conflict in root types appears (especially if to consider that I try it with one endpoint)

I don't know what you mean by Demo__Query. I reproduced your setup in apollo launchpad. It works as intended, and there is no Demo__Query type if this is what you meant.

from graphql-weaver.

terion-name avatar terion-name commented on July 28, 2024

You should use typePrefix in conjunction with namespaces to avoid these kind of conflicts

understood, thank you

I don't know what you mean by Demo__Query

This:
2018-01-17 11 41 53
2018-01-17 11 42 00

But yes, queries work ok:
2018-01-17 11 44 57

And this looks strange

from graphql-weaver.

Yogu avatar Yogu commented on July 28, 2024

Ah, I only just realized you used Demo__ as typePrefix. I wondered where these two underscores come from ;)

What exactly does look strange to you, then? The Query type is the root type and contains a field for the namespace demo of type Demo__Query, which is just the renamed type Query from your endpoint.

In case you are referring to _extIntrospection - this is a field required for the @link and @join features. We could also add an option to exclude this from the output if it bothers you.

from graphql-weaver.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.