Skip to content

Add unique-names anchor to fragments docs #13336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
atharv-sys32 wants to merge 4 commits into from
+12 −0
Closed

Add unique-names anchor to fragments docs #13336

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f804370
Add unique-names anchor to fragments docs so graphql-tag warning link…
atharv-sys32 Jul 15, 2026
b863bfb
Fix phrasing per CodeRabbit review — remove 'different field selectio…
atharv-sys32 Jul 15, 2026
27a6ae5
docs: improve fragment names section phrasing
atharv-sys32 Jul 24, 2026
94ef9f4
fix: address maintainer review feedback
atharv-sys32 Jul 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/source/data/fragments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,18 @@

Changes to the `NameParts` fragment automatically update the fields included in any operations that use it. This reduces the effort required to keep fields consistent across a set of operations.

## Unique fragment names {#unique-names}

Fragment names must be unique across your entire application. If you reuse a fragment name, the `graphql-tag` library warns about the conflict at runtime to help prevent bugs:

Check notice on line 46 in docs/source/data/fragments.mdx

View check run for this annotation

Apollo Librarian / AI Style Review

docs/source/data/fragments.mdx#L46 

**Framing Apollo Products**: Focus on the benefit of the tool helping the user rather than the negative aspect of a conflict or bug.

**Framing**: Frame content relative to the reader by using "you" and "your".

**Products and Features**: Do not use articles like "the" before standalone product or library names like graphql-tag.

**Voice**: The original phrasing is slightly passive. Using 'always' and 'to prevent' provides a more authoritative and helpful tone.

**Word and Symbol Usage**: Avoid semicolons; a period and new sentence is clearer.

```suggestion
Fragment names must be unique across your entire application. If you reuse a fragment name, the `graphql-tag` library provides a warning about the conflict at runtime to help you identify the issue:
```

```text
Warning: fragment with name SomeFragment already exists.
graphql-tag enforces all fragment names across your application to be unique; read more about
this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names
```

As a best practice, use descriptive, component-scoped fragment names (like `ItemFragment` or `UserProfileFragment`) to avoid name collisions.

## Example usage

Let's say we have a blog application that executes several GraphQL operations related to comments (submitting a comment, fetching a post's comments, etc.). Our application likely has a `Comment` component that is responsible for rendering comment data.
Expand Down