Skip to content

chore: final tokensChainsCache cleanup#28789

Draft
juanmigdr wants to merge 16 commits intomainfrom
chore/final-tokensChainsCache-cleanup
Draft

chore: final tokensChainsCache cleanup#28789
juanmigdr wants to merge 16 commits intomainfrom
chore/final-tokensChainsCache-cleanup

Conversation

@juanmigdr
Copy link
Copy Markdown
Member

@juanmigdr juanmigdr commented Apr 14, 2026

Description

Changelog

CHANGELOG entry:

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-3058

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

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

Medium Risk
Touches transaction labeling and smart-contract detection logic; while mostly cleanup, it could change UI strings and increase reliance on RPC getCode calls if any callers previously benefited from the cache shortcut.

Overview
Completes the tokensChainsCache deprecation by deleting selectors/tokenListController.ts and stripping TokenListController.tokensChainsCache from mocks, fixtures, Sentry allowlists, and snapshot expectations.

Updates asset/transaction code paths to stop reading token metadata from the token-list cache: selectAsset now sources aggregators from TokensController.allTokens, decodeConfirmTx no longer prefixes actionKey with a cached token symbol, and isSmartContractAddress removes the mainnet “in cache” fast-path so contract detection always checks on-chain code. Related tests are adjusted accordingly.

Reviewed by Cursor Bugbot for commit c4c505c. Bugbot is set up for automated code reviews on this repo. Configure here.

@juanmigdr juanmigdr requested review from a team as code owners April 14, 2026 07:35
@github-actions github-actions Bot added size-S risk-low Low testing needed · Low bug introduction risk labels Apr 14, 2026
@juanmigdr juanmigdr requested review from a team as code owners April 14, 2026 07:59
@github-actions github-actions Bot added size-M risk-low Low testing needed · Low bug introduction risk and removed size-S risk-low Low testing needed · Low bug introduction risk labels Apr 14, 2026
Comment thread app/components/Views/WalletActions/WalletActions.test.tsx Outdated
@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-low Low testing needed · Low bug introduction risk labels Apr 14, 2026
Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

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.

There are 2 total unresolved issues (including 1 from previous review).

Fix All in Cursor

❌ 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 c61ce58. Configure here.

const renderTo = renderFullAddress(to);
const chainId = txChainId;

const tokenList =
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Unused chainId variable after tokensChainsCache removal

Low Severity

The const chainId = txChainId assignment is now dead code. It was previously used only for the tokensChainsCache lookup that was removed in this cleanup. The variable is assigned but never read in this function scope (txChainId is referenced directly at line 884 for transactionDetails).

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit c61ce58. Configure here.

@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-medium Moderate testing recommended · Possible bug introduction risk labels Apr 14, 2026
@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-medium Moderate testing recommended · Possible bug introduction risk labels Apr 14, 2026
@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-medium Moderate testing recommended · Possible bug introduction risk labels Apr 15, 2026
@juanmigdr juanmigdr requested a review from a team as a code owner April 15, 2026 13:32
@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-medium Moderate testing recommended · Possible bug introduction risk labels Apr 15, 2026
@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-medium Moderate testing recommended · Possible bug introduction risk labels Apr 15, 2026
@github-actions github-actions Bot added risk-medium Moderate testing recommended · Possible bug introduction risk and removed risk-medium Moderate testing recommended · Possible bug introduction risk labels Apr 16, 2026
@juanmigdr juanmigdr marked this pull request as draft April 16, 2026 14:25
@github-actions
Copy link
Copy Markdown
Contributor

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - draft PR

All E2E tests pre-selected.

View GitHub Actions results

@sonarqubecloud
Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
D Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@github-actions
Copy link
Copy Markdown
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk-medium Moderate testing recommended · Possible bug introduction risk size-M team-assets

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants