GraphQL Fragment Generator

A GraphQL fragment is a reusable selection set that you define once and spread across multiple queries or mutations with the `...FragmentName` syntax. Fragments keep your queries DRY: when your User type changes, you update one fragment instead of a dozen query strings. They also make it easier to co-locate data requirements with UI components — a pattern strongly recommended by Apollo, urql, and Relay.

Named fragments (`fragment UserFields on User { ... }`) are defined separately and can be reused across many operations. Inline fragments (`... on User { ... }`) are written directly inside a query and are not reusable. Inline fragments are mainly used for type-narrowing inside union and interface fields, while named fragments are the go-to choice for code reuse and component-driven data fetching.

Enable it when you want fully self-contained fragments that resolve nested object fields immediately. This generates a separate fragment for each nested type (e.g. `AddressFields`) and spreads it inside the parent fragment. Disable it when you prefer shallow fragments and want to explicitly choose which nested fields to include per query — the generator will leave a comment placeholder instead so you know which fields require expansion.

__typename tells Apollo Client (and other normalized caches) exactly which type each object is, which is required for correct cache normalization and for type-safe union/interface handling. It is also required if you use Apollo's `possibleTypes` or Relay's store-based fragments. Enabling this option is a good default for any Apollo or Relay project. For urql with the document cache (non-normalized), __typename is less critical.

Yes. The generated fragments are standard GraphQL SDL and work with any GraphQL client. With Apollo Client you import the fragment from a `.gql` / `.graphql` file and spread it inside your query document. With urql you do the same via `gql` tagged templates. Relay requires fragments to be co-located with components and uses its own compiler, but the fragment SDL itself is identical — you just wrap it in Relay's `graphql` tag and call `useFragment`.