Skip to content

refactor(tron-wallet-snap): organize handlers and rename asset reader functions - #90

Open
ulissesferreira wants to merge 4 commits into
mainfrom
WPN-1497-handlers-and-renames
Open

refactor(tron-wallet-snap): organize handlers and rename asset reader functions#90
ulissesferreira wants to merge 4 commits into
mainfrom
WPN-1497-handlers-and-renames

Conversation

@ulissesferreira

@ulissesferreira ulissesferreira commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Move handlers into dedicated folders (handlers/assets/, cronjob/, keyring/, user-input/) with explicit import paths
Old New
Screenshot 2026-07-31 at 22 41 37 Screenshot 2026-07-31 at 22 40 24
  • Rename AssetsService account readers: getAccountAssets, getAccountAssetsByIDs, getAccountAssetByID
  • No runtime behavior change

Jira

Test plan

  • yarn workspace @metamask/tron-wallet-snap build
  • yarn workspace @metamask/tron-wallet-snap run test

Part of the AssetsController migration split stack (Step 1/3).

Pure organizational move with import path updates only. No AssetsService
API renames or behavior changes.
Align public reader names with the final AssetsController-oriented API:
getAccountAssets, getAccountAssetsByIDs, getAccountAssetByID.
Handler folder move requires importing from ../cronjob/cronjob rather
than the bare folder path so the Snap bundle resolves correctly.
Handler files moved into subfolders in WPN-1497, so point eslint
suppressions at the new paths and refresh snap.manifest.json after
the handler import path fix changed the bundle hash.
@ulissesferreira
ulissesferreira requested a review from a team as a code owner July 31, 2026 21:48
@ulissesferreira ulissesferreira changed the title refactor(tron-wallet-snap): organize handlers and rename asset readers (WPN-1497) refactor(tron-wallet-snap): organize handlers and rename asset reader functions Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant