Skip to content

feat(skills-next): add flutter SDK references#242

Open
evanpurkhiser wants to merge 1 commit into
mainfrom
evanpurkhiser/feat-skills-next-add-flutter-sdk-references
Open

feat(skills-next): add flutter SDK references#242
evanpurkhiser wants to merge 1 commit into
mainfrom
evanpurkhiser/feat-skills-next-add-flutter-sdk-references

Conversation

@evanpurkhiser

Copy link
Copy Markdown
Member

Direct LLM port of the existing flutter SDK skill into the skills-next per-SDK reference layout under skills-next/references/sdks/flutter/. This content has NOT been reviewed at all — it is a machine-generated port of the existing SDK skill, and every file should be treated as unverified.

Comment thread skills-next/references/sdks/flutter/logging.md Outdated
Comment thread skills-next/references/sdks/flutter/logging.md Outdated
Comment thread skills-next/references/sdks/flutter/logging.md Outdated
@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/feat-skills-next-add-flutter-sdk-references branch from a1ee41f to 689a3bf Compare July 2, 2026 21:14
@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/feat-skills-next-add-flutter-sdk-references branch from 689a3bf to 032f3e1 Compare July 7, 2026 15:16

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 032f3e1. Configure here.

|-------|----------|
| No transactions in Sentry | Confirm `tracesSampleRate > 0`; set to `1.0` to see all during debugging |
| Navigation not tracked | Add `SentryNavigatorObserver()` to `navigatorObservers`; name all routes |
| Traces not being connected across navigations | `enableNewTraceOnNavigation` defaults to `false` since 9.19.0 — set it to `true` to generate a fresh trace on each navigation event |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inverted navigation trace fix

Medium Severity

The troubleshooting row for traces not connecting across navigations tells readers to set enableNewTraceOnNavigation to true, which starts a new trace on each navigation and reduces continuity. Keeping it false (the 9.19+ default) is what preserves connected traces.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 032f3e1. Configure here.

@evanpurkhiser

Copy link
Copy Markdown
Member Author

Automated fixes pushed addressing the review feedback on this PR:

  • logging.md: removed the orphaned }); (Dart syntax error); fixed the logging-package _logger.info('msg', {map}) misuse (a Map was passed where an error object is expected); and converted every direct Sentry.logger.* snippet to the real named attributes: parameter wrapping values with SentryAttribute.string/int/double/bool.

Note: the bot's Sentry.logger.warn() -> warning() suggestion is a false positive. Verified against sentry-dart source (SentryLogger interface, DefaultSentryLogger, and the unit tests): warn is the real method and warning does not exist, so it was left as-is.

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.

1 participant