If I change the url in the options of the gatsby-source-graphql plugin, and use a totally different url for the createLocalLink function, the content fetched will be the right one but the function will use the url provided in the gatsby-source-graphql rather than one specified in the createLocalLink function by means of utils and config files.
Of course you would never used two different urls but I wonder why Gatsby is using the one on gatsby-config.js rather than the one in config.js
Following the issue with Transform node fields with gatsby-source-graphql I realised something else might not be right.
If I change the url in the options of the gatsby-source-graphql plugin, and use a totally different url for the
createLocalLinkfunction, the content fetched will be the right one but the function will use the url provided in the gatsby-source-graphql rather than one specified in thecreateLocalLinkfunction by means of utils and config files.Of course you would never used two different urls but I wonder why Gatsby is using the one on gatsby-config.js rather than the one in config.js