Currently, you point to a single schema in a codebase which is fine for most, but we're using a monorepository to share code between multiple brands using NX.
Example folder structure:
/apps
brand-a
brand-b
/libs
common-utils
a-atoms
a-molecules
b-atoms
b-molecules
Brand A and B share common utilities and more, and each brand has it's own schema/API and UI components.
We'd like to be able to do something like this:
apollo.config.json:
{
"clients": [
{
"service": "brand-a@production",
"includes": [
"/apps/brand-a/**/*.graphql",
"/libs/a-atoms/**/*.graphql",
"/libs/a-molecules/**/*.graphql"
]
},
{
"service": "brand-b@production",
"includes": [
"/apps/brand-b/**/*.graphql",
"/libs/b-atoms/**/*.graphql",
"/libs/b-molecules/**/*.graphql"
]
}
]
}
Currently, you point to a single schema in a codebase which is fine for most, but we're using a monorepository to share code between multiple brands using NX.
Example folder structure:
Brand A and B share common utilities and more, and each brand has it's own schema/API and UI components.
We'd like to be able to do something like this:
apollo.config.json:
{ "clients": [ { "service": "brand-a@production", "includes": [ "/apps/brand-a/**/*.graphql", "/libs/a-atoms/**/*.graphql", "/libs/a-molecules/**/*.graphql" ] }, { "service": "brand-b@production", "includes": [ "/apps/brand-b/**/*.graphql", "/libs/b-atoms/**/*.graphql", "/libs/b-molecules/**/*.graphql" ] } ] }