Skip to content

chore(core): resolve stale TODO comments - #6819

Merged
antonis merged 1 commit into
mainfrom
chore/resolve-stale-todos
Oct 1, 2026
Merged

antonis merged 1 commit into
mainfrom
chore/resolve-stale-todos

Conversation

@antonis

@antonis antonis commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring

📜 Description

Resolves four stale or answerable TODO comments after verifying each against the source. Comment-only — no behavior change.

File Old TODO Resolution
tracing/reactnavigation.ts, tracing/reactnativenavigation.ts // TODO: What if it's not SentrySpan? The latest navigation span is always a SentrySpan or a SentryNonRecordingSpan; the latter's end() is a no-op, so there's nothing to discard. Replaced with a one-line note at the guard.
tracing/reactnativenavigation.ts // TODO: Should we include pass props? passProps is arbitrary app-defined data (potential PII), so it's intentionally omitted. Documented so it isn't added back unguarded.
ios/RNSentry.mm // TODO: If the callback isn't executed the promise wouldn't be resolved. Stale — resolve() is unconditional. Removed the comment.

💡 Motivation and Context

TODO cleanup pass

💚 How did you test it?

  • yarn lint (oxlint + format) — clean
  • clang-format on RNSentry.mm — clean
  • yarn jest navigation suites — 135 passing
  • Comment/no-op change: no runtime behavior affected.

📝 Checklist

  • I added tests to verify changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • All tests passing.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.
  • No breaking changes.

🔮 Next steps

Resolve four stale/answerable TODOs after verifying each against the source:

- reactnavigation.ts / reactnativenavigation.ts "What if it's not SentrySpan?":
  the latest navigation span is always a SentrySpan or a SentryNonRecordingSpan,
  and the latter's end() is a no-op, so there is nothing to discard. Replaced
  with a one-line note at the guard.
- reactnativenavigation.ts "Should we include pass props?": passProps is
  arbitrary app-defined data (potential PII), so it is intentionally omitted.
  Documented as a one-line note so it is not added back unguarded.
- RNSentry.mm "If the callback isn't executed the promise wouldn't be resolved":
  stale — resolve() is unconditional, and cocoa's configureScope runs the block
  synchronously when the SDK is initialized (nil scope otherwise, which the JS
  consumer already handles). Removed the stale comment.

Comment-only; no behavior change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor
Fails
🚫 Pull request is not ready for merge, please add the "ready-to-merge" label to the pull request

Generated by 🚫 dangerJS against 708330c

@antonis
antonis marked this pull request as ready for review October 1, 2026 13:34
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

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


  • chore(core): resolve stale TODO comments by antonis in #6819
  • fix(profiling): Populate Hermes runtime version on JS profiles by antonis in #6817

🤖 This preview updates automatically when you update the PR.

@antonis
antonis merged commit a73e0fe into main Oct 1, 2026
70 of 78 checks passed
@antonis
antonis deleted the chore/resolve-stale-todos branch October 1, 2026 13:59
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