Allow different schemas for different file paths

[kedarguy]

Example use case:

Next.js app where the API routes can call the graphql API as admins vs the frontend that can call the API as authenticated users.

Example config from graphql-code-generator config which allows a similar behaviour:

module.exports = {
  generates: {
    './types/codegen/index.ts': {
      schema: [
        {
          [`https${process.env.NEXT_PUBLIC_API_URL}`]: {
            headers: {
              'X-Hasura-Admin-Secret': XXXXXX,
              'X-Hasura-Role': 'User',
            },
          },
        },
      ],
      documents: [
        './pages/**/*.tsx',
        './components/**/*.tsx',
        './utils/**/*.tsx',
      ],
    },
    './types/codegen/admin-generated.ts': {

      schema: [
        {
          [`https${process.env.NEXT_PUBLIC_API_URL}`]: {
            headers: {
              'X-Hasura-Admin-Secret': XXXXXX,
              'X-Hasura-Role': 'Admin',
            },
          },
        },
      ],
      documents: ['./pages/api/**/*.ts'],
    },
  },
};

┆Issue is synchronized with this Jira Task by Unito