require graphql import from gatsby to use

[jquense]

This is a pretty big breaking change, and I can walk back some of it so it can be made compatible (like a config setting to require the import).

I need to make a gatsby site that works with relay/apollo on the client in the very near future but that isn’t possible at the moment because gatsby assumes all graphql tags are its own.

[jquense]

As a less severe change, we could also assume global i.e. unreferenced graphql tags are gatsby's and leave any alone that are referenced (like from 'relay' or apollo packages)

[KyleAMathews]

I need to make a gatsby site that works with relay/apollo on the client in the very near future

💯 to this so let's make this possible.

Perhaps we deprecate auto-supporting the graphql tag in v2 and then require it in v3?

[KyleAMathews]

Also 💯 to making the graphql tag seem less magical (even though it still will be under the hood).

[jquense]

I can't seem to get a local test up running using this...lets see if netlify works nothing should break

[jquense]

w/y/t ?

[pieh]

I like it! For this maybe we could do some codemod-esque utility to auto update people's code (maybe not print out deprecation warning until we have this tool)? Less magic that seems to come from nowehere is always good

[jquense]

adding some robustness to this!

[jquense]

ok this covers a lot more edge cases, I wanted to write the codemod as well but ran out of time...

[KyleAMathews]

Looks great! Thanks for writing this! A number of people have complained about not being able to use Relay & Gatsby together and I think everyone has complained about graphql being an unimported global 😅

[KyleAMathews]

I'll create a follow-up issue about updating the tutorial to account for this.

Once we have a codemod, we can run that on the example sites to update them.