Skip to content

fix(names): Correct graphql span name examples - #573

Merged
andreiborza merged 1 commit into
mainfrom
ab/graphql-name-examples
Aug 25, 2026
Merged

andreiborza merged 1 commit into
mainfrom
ab/graphql-name-examples

Conversation

@andreiborza

Copy link
Copy Markdown
Member

Description

The graphql span name examples are mutation and query, which neither template can produce: Sentry prefixes GraphQL span names with GraphQL , as the otel_notes on the same entry says. They predate that prefix.

Replaces them with names the templates actually produce, and includes the static fallback, matching how sibling name conventions list their examples (browser.json lists Pageload, db.json lists Database operation).

No template or behavior change.

PR Checklist

  • I have run yarn test and verified that the tests pass.
  • I have run yarn generate to generate and format code and docs.

https://claude.ai/code/session_013bjBXkGkJo8eL8hkz48byi

The examples were `mutation` and `query`, which no template can produce
since Sentry prefixes GraphQL span names with `GraphQL `. They predate
that prefix.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013bjBXkGkJo8eL8hkz48byi
@github-actions

Copy link
Copy Markdown

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


Bug Fixes 🐛

  • (names) Correct graphql span name examples by andreiborza in #573

🤖 This preview updates automatically when you update the PR.

@andreiborza
andreiborza marked this pull request as ready for review August 24, 2026 18:45
@andreiborza
andreiborza requested review from a team, Lms24, cleptric, mjq and nsdeschenes as code owners August 24, 2026 18:45
@andreiborza
andreiborza merged commit a40dc1d into main Aug 25, 2026
17 checks passed
@andreiborza
andreiborza deleted the ab/graphql-name-examples branch August 25, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants