Skip to content

Add unique-names anchor to fragments docs #13365

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

Merged
jerelmiller merged 3 commits into from
Jul 30, 2026
+14 −0
Merged

Add unique-names anchor to fragments docs #13365

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e06ec68
Add unique-names anchor to fragments docs
atharv-sys32 Jul 28, 2026
b0aa430
Move to troubleshooting section
jerelmiller Jul 30, 2026
100510c
Update from suggestions
jerelmiller Jul 30, 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
14 changes: 14 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 @@ -1790,3 +1790,17 @@
- `Unmasked<TData>` - Unwraps `TData` into the full result type

For more information about other overridable types in Apollo Client, see the [TypeScript guide](../development-testing/static-typing).

## Troubleshooting

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

View check run for this annotation

Apollo Librarian / AI Style Review

docs/source/data/fragments.mdx#L1794 

**Structural Elements**: Conceptual overview headings should use gerunds.

```suggestion
## Troubleshoot fragments
```

### Unique names

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

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

View check run for this annotation

Apollo Librarian / AI Style Review

docs/source/data/fragments.mdx#L1798 

**Products and Features**: Do not use code formatting or backticks for standalone product or feature names like graphql-tag.

**Verb Tense and Voice**: Use present tense instead of 'provides a warning'.

**Voice**: Use an authoritative tone to prescribe the correct approach for fragment naming.

**Word and Symbol Usage**: Avoid semicolons; use a period to separate independent clauses for better clarity.

```suggestion
Fragment names must be unique across your entire application. If you reuse a fragment name, graphql-tag 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 `CartItemFragment` or `UserProfileCardFragment`) to avoid name collisions.
Loading