Repository navigation
Conversation
micaelae
force-pushed
the
swaps5184-trace-tags
branch
from
October 19, 2026 21:06
a307ca8 to
751e316
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ef7c179. Configure here.
micaelae
enabled auto-merge
October 19, 2026 22:43
GeorgeGkas
approved these changes
Oct 20, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Oct 20, 2026
This branch was successfully deployed
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
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.

Explanation
Adds Sentry tags to swap/bridge traces that indicate the active feature (swap, batch sell, quick buy, etc). The tags can be used to filter traces in in Sentry.
This change also exports shared trace types (
SwapTraceRequest,SwapTraceFunction,TraceFeatureTag) so mobile and extension send the same tags.Client PRs
References
Fixes https://consensyssoftware.atlassian.net/browse/SWAPS-5184
Checklist
Note
Medium Risk
Breaking API change for all BridgeController and BridgeStatusController consumers that must supply traceFn; telemetry behavior changes but core swap/bridge logic is largely unchanged aside from sync trace calls and error swallowing on quote paths.
Overview
Standardizes swap/bridge Sentry tracing so controllers and clients share typed trace contracts and consistent feature tagging.
BridgeControllerandBridgeStatusControllernow require atraceFnat construction (the previous optional no-op default is removed). Controllers use a sharedSwapTraceFunction/SwapTraceRequestshape that mandatestags.feature, populated from the activefeature_idviaBRIDGE_FEATURE_ID_TO_FEATURE_TAG(exported asSwapFeatureTagalong with related trace name helpers).Quote and transaction traces in both packages now attach
tags: { feature: 'swap' | 'batch_sell' | ... }on events such as quote fetch, provider first result, and swap/bridge transaction completion.bridge-controlleralso expands exportedTraceNamevalues for client-side traces and wraps telemetry in try/catch so a failingtraceFncannot break quote fetching.Tests and changelogs are updated for the breaking constructor change and new trace payloads.
Reviewed by Cursor Bugbot for commit e0107cf. Bugbot is set up for automated code reviews on this repo. Configure here.