Skip to content

[skill-drift] update(sentry-browser-sdk): document urlQueryParams rename and new graphQL/databaseQueryData/stackFrameVariables options - #300

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
skill-drift/browser-skill-drift-update-sentry-browser-sdk-do-1785159612
Open

[skill-drift] update(sentry-browser-sdk): document urlQueryParams rename and new graphQL/databaseQueryData/stackFrameVariables options#300
github-actions[bot] wants to merge 1 commit into
mainfrom
skill-drift/browser-skill-drift-update-sentry-browser-sdk-do-1785159612

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Warning

Auto-generated from external SDK content. Review all links and code suggestions before acting on them.

Warning

Auto-generated from external SDK content. Review all links and code suggestions before acting on them.

What changed upstream

@sentry/browser (via @sentry/core) shipped several related changes to the dataCollection init option, released in 10.66.0/10.67.0/10.68.0:

  • queryParams renamed to urlQueryParams (#22217, released 10.67.0). queryParams still works but is now marked @deprecated in favor of the new name; same shape (boolean | { allow: string[] } | { deny: string[] }) and default (true).
  • New dataCollection.graphQL option (#22221, released 10.66.0) — { document?: boolean; variables?: boolean }, both default true. Controls whether GraphQL document text and operation variables are attached when a GraphQL integration is enabled. Does not add instrumentation on its own.
  • New dataCollection.databaseQueryData option (#22219, released 10.66.0) — boolean, default true. Controls collection of DB query parameters, inline literal values, mutation/request bodies, and returned result data. Sanitized db.query.text and structural metadata are always collected regardless of this flag.
  • stackFrameVariables now accepts a CollectBehavior, not just a boolean (#22526, released 10.68.0). { allow: string[] } | { deny: string[] } filters captured local variables by name. Note: filtering matches names after bundling/minification, so source-level variable names may not match at runtime.

Verified directly against packages/core/src/types/datacollection.ts at the 10.68.0 release tag.

What was out of date

src/references/sdks/browser/index.md's dataCollection Options table still listed only the deprecated queryParams field, had no rows for graphQL or databaseQueryData, and documented stackFrameVariables as a plain boolean.

Fix

Updated the table in src/references/sdks/browser/index.md:

  • Replaced the queryParams row with urlQueryParams (noting the deprecation and min version) and added a deprecation callout below the table.
  • Added graphQL and databaseQueryData rows with defaults and minimum SDK versions.
  • Updated the stackFrameVariables row to document the new CollectBehavior filtering shape and the bundling/minification caveat.
  • Updated the inline dataCollection example to use urlQueryParams instead of the deprecated queryParams.

No other file in the browser reference tree mentions queryParams/urlQueryParams/graphQL/databaseQueryData/stackFrameVariables, so no other edits were needed.

Other PRs reviewed but not actioned

  • #22572 feat(core)!: Default attachStacktrace to true — real breaking change to a documented option (attachStackTrace default flips from false to true), but merge commit 5ff9fd0 is not yet contained in the latest release tag 10.68.0 (compare status: diverged) — unreleased, so left for a future run once it ships.
  • #22557 feat(opentelemetry)!: Remove SentrySpanProcessor & SentrySampler and #22528 feat(core)!: Remove kind for spans, move to sentry.kind attribute — internal/OTel-surface changes not exposed through the browser SDK's documented public API.
  • #22527 fix(v10/core): Avoid functionToStringIntegration causing infinite recursions — bug fix to a default integration, no documentable behavior change.
  • #22533/#22564 http.route/url.full/url.path on http.server spans — server-side (Node/http.server) only, not applicable to @sentry/browser.

Note: this is the same underlying dataCollection drift already flagged for @sentry/react in PR #293 (still open) — that PR explicitly called out browser as needing the analogous fix.

Source PRs

Source PRs

…ame and new graphQL/databaseQueryData/stackFrameVariables options

Automated drift-fix run.

Co-Authored-By: Claude (claude-sonnet-5) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants