Client options are overriding each other

[drewbaker]

So today I noticed that if you specify multiple clients, that the options for the second client become the options for all clients.

For example, here is the config I have:

/*
    graphql: {
        clients: {
            default: {
                endpoint: process.env.GQL_ENDPOINT,
                options: {
                    credentials: "include",
                    mode: "cors",
                },
            },
            shopify: {
                endpoint: process.env.SHOPIFY_ENDPOINT,
                options: {
                    credentials: "same-origin",
                    mode: "cors",
                    headers: {
                        "Content-Type": "application/json",
                        "X-Shopify-Storefront-Access-Token":
                            process.env.SHOPIFY_TOKEN,
                    },
                },
            },
        },
    },

The default client will actually send the headers that are defined in the Shopify client. Am I doing something wrong here? Or is this intended behavior?

I found this out because my default client is a CMS, and that server was complaining about the X-Shopify-Storefront-Access-Token being included in the request headers.

I noticed that if you change the order of the config, it's always the second one that overrides the first.

[Gomah]

Fixed in v4.2.1