How can I access request header in ".meshrc.ts" file?

[mnlbox]

Hi guys,

First of all thanks for this awesome project. I really love it. ❤️ ❤️ ❤️

I personally prefer to use .meshrc.ts rather than .meshrc.yaml because I really like to use the typescript and IDE auto-completion feature when working on a mesh config file. But I have some difficulty as all of the examples and CodeSandbox and ... is based on .meshrc.yaml file.
So as a suggestion: I suggest adding more examples and docs regarding using javascript and typescript for GraphQL Mesh.
And now let's back to my question:
I wanna pass an api-key from my supergraph header request (mesh project) to one of my subgraphs (a graphql handler) I tried to pass it like this:

import type { YamlConfig } from '@graphql-mesh/types';


const config: YamlConfig.Config = {
  sources: [
    {
      name: 'My GraphQL SubGraph 1',
      handler: {
        graphql: {
          method: 'POST',
          retry: 5,
          endpoint: '<API endpoint>',
          schemaHeaders: {
            'api-key': process.env.API_KEY
          },
          operationHeaders: {
            'api-key': process.context.headers['api-key']   <------ This one is wrong
          }
        },
      },
    },
  ],
....
};

export default config;

But it seems this one is wrong because I have some error in my config file now. How can I access the context value here??

operationHeaders: {
    'api-key': process.context.headers['api-key']   <------ This one is wrong
  }

For the .meshrc.yaml file there are an example in the docs and the way it's working is like this:

operationHeaders:
          Authorization: Bearer {context.headers['x-my-api-token']}

But it seems this format is not working for .meshrc.ts config file. I also tried context.headers['api-key'] and this..context.headers['api-key'] but these are not working. Any idea for this?

[ardatan]

process.context.headers['api-key']
I am not sure where you found this but we don't have a usage like that. String interpolation can be used as-is.
In YAML, Bearer {context.headers['x-my-api-token']} is a string. So it should be a string in other formats as well;

'api-key': "Bearer {context.headers['x-my-api-token']}"

[mnlbox]

Yeah I also tried this one before like below (without Bearer part as I don't need that for my api-key):

          schemaHeaders: {
            'api-key': process.env.API_KEY
          },
          operationHeaders: {
            'api-key': "{context.headers['api-key']}"
          }

But the problem is that it seems operationHeaders is not working at all because currently schemaHeaders is also applied as operationHeaders for me, so even if I don't set any api-key on the request header section in the playground for a query, I'm still able to call the query and get the result.