refactor(tron-wallet-snap): extract SnapAssetsAdapter from existing AssetsService logic - #91
Conversation
53be776 to
b517134
Compare
2960d5a to
414cba1
Compare
8b77a78 to
30a99f6
Compare
414cba1 to
0e17e41
Compare
30a99f6 to
4e73383
Compare
|
@cursoragent rebase with latest main |
|
Rebased onto latest Rebase
Shasum fixAfter the rebase, CI failed on the manifest shasum (same issue as before — Linux CI uses secret mainnet RPC URLs). Updated to the CI-expected value:
Verification
|
a6cbab4 to
e34f69c
Compare
|
@cursoragent rebase latest main resolving conflicts, lint and update shasum |
|
Rebased onto latest Rebase
ShasumLinux CI uses secret mainnet RPC URLs, so the local shasum (
Verification
|
da939f6 to
cb7a717
Compare
|
Few comments:
|
|
5e27de9 to
9532cbd
Compare
Makes sense. |
|
@cursoragent rebase with latest main, make sure lint is good and then babysit the PR until green |
|
Rebased onto latest Rebase
Lint & tests
ShasumLinux CI uses secret mainnet RPC URLs, so the local value did not match. Updated to the CI-expected value:
CI status — greenAll 49 checks passed (0 failed), including:
PR is mergeable ( |
9532cbd to
7ac16ca
Compare
…rvice Move existing assets logic into SnapAssetsAdapter and keep AssetsService as a thin facade that always delegates to the Snap adapter. Behavior unchanged; prepares for a later Core adapter / feature-flag routing PR.
Adapter lives one directory deeper than AssetsService; bump client, constants, and types imports to ../../../ and ../types respectively.
Update the manifest shasum, cover AssetsService facade delegation in tests, and use SnapAssetsAdapter.isFiat inside the adapter implementation.
Move import suppressions to SnapAssetsAdapter and align test assertions with jest prefer-strict-equal rules.
Co-authored-by: Ulisses Ferreira <ulisses@hey.com>
a122613 to
772082a
Compare
Co-authored-by: Ulisses Ferreira <ulisses@hey.com>
## Explanation This PR updates the Stellar transaction simulation layer to not require an envelope memo for self-payments / self path-payments even when the involved account has memo_required set (SEP-29), aligning memo enforcement with inbound transfers from other accounts. <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them


Summary
adapters/SnapAssetsAdapter.tsAssetsServicewith a thin facade that delegates all public methods to the snap adapterJira
Test plan
yarn workspace @metamask/tron-wallet-snap buildyarn workspace @metamask/tron-wallet-snap run testStacks on #90 (Step 2/3).