[Subgraphs] - Using multiple query fields with different name per subgraph

[2snEM6]

Let's say I have two subgraphs:

• admin
• public

Each subgraph must have a login query field, but currently Pothos complains about it: Duplicate field definition for field login in Query

How can I do that?

Thanks!

[hayes]

The subgraph plugin is exclusively for creating subsets of your graph. You would only define 1 login field and include it as part of both subgraphs.

The subgraph plugin pre-dates apollos use of the term subgraph for federation, and the meaning there is a bit different than how it was used in Pothos.

[hayes]

add-graphql can add any GraphQL type to pothos I think, but the way you would use it would be to add everything except the query and mutation types

[2snEM6]

Thanks, that makes sense.

I was also wondering how to delete Query Fields from an existing builder instance and I assume it's not possible, since the pendingFields map is not public. Only the getFields is and it always displays an empty map

[hayes]

Yeah, currently this isn't really possible. The functions that define fields aren't actually run until the schema gets built. This helps with circular references/imports, but does mean that you can't really remove the fields since they aren't actually defined until you start the build process

[2snEM6]

So what I did is make sure the schema is built before reusing the builder again. Then, creating a function that does this:

  removeQueriesAndMutations(): this {
    this.configStore.typeConfigs.forEach((typeConfig) => {
      if (typeConfig.kind === 'Query' || typeConfig.kind === 'Mutation') {
        this.configStore.typeConfigs.delete(typeConfig.name);
      }
    });

    this.queryType({
      subGraphs: [...SUBGRAPHS],
      defaultSubGraphsForFields: [],
    });

    this.mutationType({
      subGraphs: [...SUBGRAPHS],
      defaultSubGraphsForFields: [],
    });

    const queryFields = this.configStore.getFields('Query', 'Object');
    queryFields.forEach((field) => {
      queryFields.delete(field.name);
    });

    const mutationFields = this.configStore.getFields('Mutation', 'Object');
    mutationFields.forEach((field) => {
      mutationFields.delete(field.name);
    });

    this.asyncTasks = [];

    return this;
  }

[hayes]

That will probably work for now, but just a heads up that a lot of these internal APIs are changing a lot in 4.0 (no eta, but there is a v4 branch with most of the expected changes)

[2snEM6]

I extend the Builder class and added the following function:

  subgraph(name: string) {
    this.currentSubgraph = name;
    return this.removeQueriesAndMutations();
  }

Which in turn can be used as such:

const builder = new Builder();

const subgraphA = builder.subgraph("admin");

const schemaA = subgraphA.toSchema();

const subgraphB = builder.subgraph("public");

const schemaB = subgraphB.toSchema();

[2snEM6]

That will probably work for now, but just a heads up that a lot of these internal APIs are changing a lot in 4.0 (no eta, but there is a v4 branch with most of the expected changes)

Cool! thanks for the heads up. Looking forward to v4!