@graphql-tools/load detect type conflicts

[tlivings]

Is there an option to throw on type conflicts, ideally non-root types? For example:

File 1

type Query {
  a: A
}

type A {
  field: String
}

and File 2

type Query {
  a: A
}

type A {
  otherField: String
}

When loaded using loadSchema it will result in Query and A being merged together.

The question then, is there a way to force an error on type A as a conflict / naming collision?

The use case is to enforce explicitly extending types when that is the intent and otherwise throwing an error such that developers do not accidentally implement different types (think large scale development across many different schema files intended to merge).

[ardatan]

load package uses mergeSchemas under the hood which merges the schemas without respecting the order or extend operator, because it is basically a schema merger not a schema builder.

If you want to load parts seperately, you can use loadTypeDefs and build the schema on your own with concatAST and buildASTSchema.

const sources = await loadTypeDefs(...);
const combinedAST = sources.map(s => s.document);
const schema = buildASTSchema(combinedAST);

[tlivings]

Right, but load supports #import which would be necessary for this use case. I am probably looking for a level of control that is too complex though ... something like "merge identical types, throw on differences, ignore root types".

[ardatan]

Sorry currently import and merge packages don't work in that way.