fix: distinguish swaps trending token details source

[bfullam]

Description

This change separates swaps-trending token detail navigation from the generic explore trending flow so MetaMetrics can attribute those entry points correctly.

It adds a dedicated trending-swaps token details source, passes that source from the Bridge/Swaps trending section into TrendingTokenRowItem, and keeps the default trending source for existing explore-tab behavior. The added test coverage verifies the swaps-trending navigation params include the new source.

Changelog

CHANGELOG entry: null

Related issues

Fixes: SWAPS-4306

Manual testing steps

Feature: Swaps trending token source tracking

  Scenario: user opens token details from swaps trending
    Given the app is running and the Bridge/Swaps trending tokens section is visible
    When the user taps a token from the Bridge/Swaps trending tokens list
    Then the Asset route is opened for that token
    And the token details navigation params use the source "trending-swaps"

  Scenario: user opens token details from explore trending
    Given the app is running and the Explore trending tokens list is visible
    When the user taps a token from the Explore trending list
    Then the Asset route is opened for that token
    And the token details navigation params continue to use the source "trending"

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Low Risk
Small, scoped change to navigation params/analytics attribution with a default preserving existing behavior; minimal functional risk aside from potential analytics mislabeling if miswired.

Overview
Routes opened from the Swaps/Bridge trending tokens section now pass a dedicated token-details source value (TokenDetailsSource.TrendingSwaps) instead of the generic trending source, allowing analytics to distinguish entry points.

This introduces the new trending-swaps enum value, adds an optional tokenDetailsSource prop to TrendingTokenRowItem (defaulting to Trending), and updates tests to assert the Bridge section forwards the source and that navigation params include source: 'trending-swaps' when provided.

^{Written by Cursor Bugbot for commit 6909921. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeTrade, SmokeConfirmations, SmokeWalletPlatform
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes are analytics/tracking improvements only:

1. TokenDetailsSource enum (constants.ts): Added TrendingSwaps = 'trending-swaps' to distinguish analytics source between Explore trending and Swaps/Bridge trending.

2. TrendingTokenRowItem.tsx: Added optional tokenDetailsSource prop (defaults to TokenDetailsSource.Trending — backward compatible). The prop is passed to getAssetNavigationParams() to set the correct analytics source in navigation params.

3. BridgeTrendingTokensSection.tsx: Now passes tokenDetailsSource={TokenDetailsSource.TrendingSwaps} to TrendingTokenRowItem, so Bridge/Swaps trending tokens correctly report their analytics source.

No functional behavior changes — only analytics metadata in navigation params is affected. Default behavior of TrendingTokenRowItem is unchanged.

Tag selection rationale:

• SmokeTrade: The BridgeTrendingTokensSection is used in the Bridge/Swap view (BridgeView/index.tsx). The trending tokens section within Bridge is directly modified. SmokeTrade covers swap/bridge flows.
• SmokeConfirmations: Required per SmokeTrade tag description — "when selecting SmokeTrade for swap/bridge flows, also select SmokeConfirmations."
• SmokeWalletPlatform: The TrendingTokenRowItem is used in the Trending tab (TrendingTokensList, TrendingView/sections.config.tsx). Per tag description, changes to Trending views affect SmokeWalletPlatform.

Performance tests are not warranted — these are pure analytics metadata changes with no rendering, data loading, or performance-sensitive code paths affected.

Performance Test Selection:
Changes are limited to analytics metadata (TokenDetailsSource enum value and prop passing). No UI rendering changes, no data loading changes, no state management changes, and no performance-sensitive code paths are affected. Performance tests are not warranted.

View GitHub Actions results

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
17 value mismatches detected (expected — fixture represents an existing user).
View details

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud