Skip to content

Fixed_Typo_Update nerdgraph-explorer.mdx #22574

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
WriteMayur merged 2 commits into from
Dec 30, 2025
Merged

Fixed_Typo_Update nerdgraph-explorer.mdx #22574

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9907be5
Update nerdgraph-explorer.mdx
tsomerve Dec 24, 2025
60e4984
Linguistic enhancements
WriteMayur Dec 30, 2025
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
2 changes: 1 addition & 1 deletion src/content/docs/apis/nerdgraph/get-started/nerdgraph-explorer.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ If you're new to GraphQL, get acquainted with the GraphQL API via the NerdGraph
src="/images/apis-and-data_screenshot-full_NerdGraph-mutation-example.webp"
/>

In this case, you adding a custom tag to an entity. The editor will complain if you don't select `errors`: Mutations must have a way of telling you how the operation performed in the backend (failed requests result in null responses).
When you add a custom tag to an entity, you must select the `errors` field. Otherwise, the editor displays an error.

<Callout variant="tip">
Unlike REST, GraphQL APIs like NerdGraph can return partial responses. For example, if you try adding tags to multiple entities, some mutations can fail and others succeed; all is logged in the GraphQL response you get.
Expand Down
Loading