Using Relays in Graphql-core raises a TypeError about graphql-core HOT 4 CLOSED

I think the error message is corect. The tree of query_type.fields already includes the Query type, since it is referenced, so you can't define it again. This works, since you're using the same Query type:

GraphQLSchema(schema.get_type('Query'))

You can also remove the reference to the query type and then later add it again:

query = GraphQLObjectType('Query', {
    name: field for name, field in schema.query_type.fields.items()
    if name != 'relay'})
schema = GraphQLSchema(query)
schema.query_type.fields['relay!'] = GraphQLNonNull(query)

But I'm not sure what you actually want to achieve.

from graphql-core.

@Cito thanks for taking the time to answer. What I want to achieve that took me in this direction is a use case where I need to select, out of a big schema, just some subset of queries and mutations to obtain a smaller "scoped" schema. That's why I add the queries and mutations in that way.

I've been using a solution like the second one you propose, however, this gets complicated in some cases where the query type mentioned is nested. i.e

type Mutation {
 ....
  replaceTimeSeriesRange(
    """
    The exclusive input argument for this mutation. An object type, make sure to see documentation for this object’s fields.
    """
    input: ReplaceTimeSeriesRangeInput!
  ): ReplaceTimeSeriesRangePayload
....
}

  """All input for the `replaceTimeSeriesRange` mutation."""
input ReplaceTimeSeriesRangeInput {
  """
  An arbitrary string value with no semantic meaning. Will be included in the
  payload verbatim. May be used to track mutations by the client.
  """
  clientMutationId: String
  attributeOrTagId: BigInt
  entries: [TimeSeriesEntryInput]
  startTime: Datetime
  endTime: Datetime
}

"""The output of our `replaceTimeSeriesRange` mutation."""
type ReplaceTimeSeriesRangePayload {
  """
  The exact same `clientMutationId` that was provided in the mutation input,
  unchanged and unused. May be used by a client to track mutations.
  """
  clientMutationId: String
  json: JSON

  """
  Our root query field type. Allows us to run any query from our mutation payload.
  """
  query: Query
}

adding the mutation replaceTimeSeriesRange to a schema will raise the TypeError in a similar way.

from graphql-core.

Maybe have a look at the code of utilities.lexicographic_sort_schema and do it similary - instead of sorting fields, you would filter fields.

from graphql-core.

I'll need to check. Thanks for the hint. Closing since it's not a bug of the library.

from graphql-core.