Where should we put our graphql operations?

[esizer]

We will eventually be moving to a new configuration for graphql-codegen. While we could continue with our current way of doing things, it really encourages defining operations in a *.tsx file to leverage new features.

Since we will be changing the file type, this gives us an opportunity to decide, should we change where these operations are located?

[vd1992]

If we're going to be stitching operations together now from fragments, clustered together in a central location seems nice.

[petertgiles]

It seems like they really want to you to keep the fragment minimal and tailored to the component. It seems similar to props - keep it close to the component or move it out of the file if it gets too big.

[tristan-orourke]

I like this mindset - keep it similar to how we use props or small utility components: default to defining the fragment in the component file, and if it gets too big and complicated, it could be moved to a co-located file.

[mnigh]

@esizer can this discussion be closed?

[esizer]

We have completed the migration so this is outdated and no longer needed.