Fragment spreads are not included within the main query

[EmmanuelPonnudurai]

Hello there. Thanks for the wonderful toolset that you've created.

I am trying to generate the definitions for the queries in my application. While doing this, I notice that the results have fragments and queries separately. This makes it hard for me to tie them up together.

Consider this situation,

file1.ts

import { fragment1  } from '../../fragments/file2';

const query1 = gql`
  query myNamedQuery {
    query actualQuery {
      id
      name
      ...moreData
    }
  }
  ${fragment1}
`;

file2.ts

const fragment1 = gql`
  fragment moreData on SomeType {
    value
    someMoreData {
      foo
      bar
    }
  }
`;

Here is how I generate the definitions,

const { loadDocuments } = require('@graphql-tools/load');
const { CodeFileLoader } = require('@graphql-tools/code-file-loader');

loadDocuments('./app/**/*.ts', loaders: [new CodeFileLoader()])
.then(data => {
  // I get what I need here. 
  // However, the question I have is explained further
})

I get two items in the Source[] array. One for the query and another for the fragment.

In the first item, rawSDL is,

query myNamedQuery {
    query actualQuery {
      id
      name
      ...moreData
    }
  }

In the second item, rawSDL is,

fragment moreData on SomeType {
    value
    someMoreData {
      foo
      bar
    }
  }

My question is, why is the fragment spread definition not included within the first item as well? My expectation is to see something like this,

query myNamedQuery {
    query actualQuery {
      id
      name
      ...moreData
    }
  }

fragment moreData on SomeType {
    value
    someMoreData {
      foo
      bar
    }
  }

The reason this is important for my use case is because I need to definitively know the entire query string contents, as I must save them on the backend in advance (as part of a build step).

If I get them separately. How will I be able to know that the spread fragment with the term moreData is to be pulled from the second item. There could be another fragment definition in another file which has the same name moreData but it asks for more or less # of fields. So, I will not know which one to pick and associate properly, even if I was to manually tie them up together.

Is there some pointer or reference on the main query Source result which says this fragment spread is to be taken from this file or some way to precisely tie them up.

I tried using the graphql tag pluck option and that also doesn't yields same results. Followed the sample from here https://the-guild.dev/graphql/tools/docs/graphql-tag-pluck

Pls let me know if im taking the right direction or if there is something I'm missing.

Thanks in advance for your guidance and pointers to help me resolve this.

[ardatan]

GraphQL Tag Pluck doesn't parse documents. It extracts the GraphQL strings one by one. That's why, two different appearance of gql tag are returned as two different sources. This is the expected behavior.