docs(dart): Update stacktrace info for the logging integration#16401
Merged
docs(dart): Update stacktrace info for the logging integration#16401
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the Dart logging integration documentation by adding a new "Stack Traces" section that clarifies how stack traces are collected when using the logging integration. The documentation addresses confusion around why error events may show inaccurate stack traces and provides two clear solutions.
Changes:
- Added comprehensive documentation explaining stack trace collection behavior in the Dart logging package
- Provided two code examples demonstrating how to ensure accurate stack traces: using
recordStackTraceAtLeveland manually passing stack traces - Clarified that Sentry falls back to
StackTrace.currentwhen no stack trace is explicitly provided, which points to Sentry's internals rather than the actual call site
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
codyde
added a commit
that referenced
this pull request
Feb 19, 2026
* origin/master: docs(sdk): coordination and maintenance standards (#16463) docs(sdk): add spec format components and migrate check-ins (#16461) docs(sdk): repository and documentation standards (#16462) docs(sdk): Add issue saved replies and simplify CopyableCard (#16459) docs(sdk): add review & ci standard (#16458) fix(unity): correct lifecycle breadcrumbs docs (#16456) docs(sdk): add code quality standard (#16455) docs(sdk): migrate releases process to playbook and standard (#16447) docs(sdk): merge basics.mdx into overview.mdx (#16446) docs(sdk): remove old triaging process page (#16448) docs(dart): Update stacktrace info for the logging integration (#16401) docs(dart): Fix user attributes gated behind `sendDefaultPii` (#16407) feat(playstation): Add symbols documentation for dumps (#16454) feat(develop-docs): Restore Sentry Voice guidelines page (#16453) # Conflicts: # app/[[...path]]/page.tsx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
As it causes some confusion add more info to how stacktraces are collected using the logging integration.
Closes getsentry/sentry-dart#3499
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES