Unknown fragment error when the fragment is defined as an object field

[mdoury-oef]

Describe the bug

Attaching fragments to utils and components is quite a common composition pattern. In some cases, grouping fragments in a map could also be useful. It seems when a fragment is defined as an object field, an "Unknown fragment" error is raised.

Example

// getCountryEmoji.ts
export function getCountryEmoji(
  country: FragmentOf<typeof CountryEmojiFragment>,
) {
  const data = readFragment(CountryEmojiFragment, country);
  return data.emoji;
}

getCountryEmoji.fragment = CountryEmojiFragment;

// When the fragment is defined as an object field, we get the following error:
// Unknown fragment "CountryEmoji".
const brokenQuery = graphql(
  `
    query getCountry($code: ID!) {
      country(code: $code) {
        ...CountryEmoji
      }
    }
  `,
  [getCountryEmoji.fragment],
);

The issue can be reproduced in this codesandbox

gql.tada version

@0no-co/graphqlsp: ^1.9.1 gql.tada: ^1.4.3

Validations

• [X] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
• [X] Read the docs.
• [X] Follow our Code of Conduct