Is there any way to reuse schema.graphql files between subgraphs?

[PaulRBerg]

Suppose you have multiple subgraphs that use similar GraphQL schemas.

Is there any way to reuse schema.graphql logic between subgraphs with have overlapping logic? e.g. create a shared-schema.graphql that is imported by each schema file?

does The Graph support this #import syntax?

[mitchhs12]

Yes, you can import schemas from other subgraphs with subgraph composition (up to a maximum of 5 subgraphs) using this method here:
https://thegraph.com/docs/en/subgraphs/guides/subgraph-composition/

[PaulRBerg]

Thanks for your answer.

Unfortunately, subgraph composition isn’t quite what we need. We just want to share identical GraphQL types between otherwise unrelated subgraphs. For example, both our Sablier Flow and Sablier Lockup subgraphs define a Watcher entity:

• Flow: schema.graphql
• Lockup: schema.graphql

Can you confirm that the #import syntax is not supported by The Graph? And if that is so, do you have any plans to add support for it?

As I see it, the only viable solution now would be to write a custom script that copies code from a shared implementation file.

[PaulRBerg]

I think I found the solution - Schema Merging using @graphql/tools packages.

const path = require('path') const { loadFilesSync } = require('@graphql-tools/load-files') const { mergeTypeDefs } = require('@graphql-tools/merge') const typesArray = loadFilesSync(path.join(__dirname, './types'), { extensions: ['graphql'] }) const mergedSchema = mergeTypeDefs(typesArray); const printedSchema = print(mergedSchema); // write printedSchema to a `schema.graphql` file 

[PaulRBerg]

@mitchhs12 would you be open to a PR in your docs repo to document this functionality? The current docs on the GraphQL schema don't mention anything about code organization.