How to programatically load a schema from a gql endpoint using @graphql-inspector/core

[ericbiewener]

The CLI tool @graphql-inspector provides a diff command that allows simply passing a gql endpoint string from which it will load the schema. I would like to use the programmatic interface of @graphql-inspector/core, but I don't see a way to have the diff function it exports perform the same type of schema loading.

I have looked into the source code for the diff command in the hopes that the answer would be trivially found, but it looks like I'll need to replicate more of the internals than I'd prefer. At this point I'd rather execute the CLI tool via a child process in my node script and manually parse its stdout/stderr.

[ericbiewener]

Tried going a bit further, got close but not seeing the same result as with the diff CLI command:

const loadRemoteSchema = () => {
  const loaderRegistry = new LoadersRegistry()
  loaderRegistry.register(new UrlLoader())
  return loaderRegistry.loadSchema("<my_graphql_endpoint>", {}, false, false)
}

When running the schema produced by the above function through the programmatic diff() function from core against the AST imported directly from my local codebase, I get a bunch of DANGEROUS criticality errors. 72 are of type DIRECTIVE_USAGE_FIELD_DEFINITION_REMOVED, while the other 2 are of type DIRECTIVE_USAGE_OBJECT_REMOVED.

Strangely, if I write these ASTs to files via the graphql package's printSchema function, and then pass those two files into the diff cli command, I get a "no changes" result. When doing a pure text diff on the two printed schemas, I see that the one imported from my local code as a number of directives marked as repeatable while the remote one does not. Otherwise, no differences.