feat(WPN-1652): add Core messenger plumbing for Solana AssetsProvider - #122
Draft
ulissesferreira wants to merge 1 commit into
Conversation
Wire endowment:messenger, AssetsProvider, and RemoteFeatureFlagsProvider following the Tron WPN-1497 pattern. Providers are injected into AssetsService but Snap-owned reads remain the sole production path. Migrated from MetaMask/snap-solana-wallet#637 (Tron-style AssetsProvider instead of a literal CoreAssetsAdapter). Co-authored-by: Ulisses Ferreira <ulisses@hey.com>
4 tasks
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
Part of migrating the Solana assets-controller staged migration from snap-solana-wallet#637 into this monorepo (PR 3 of 6, Lane A / feature-flag path only).
Follows the Tron
WPN-1497messenger plumbing pattern (#95) rather than a literalCoreAssetsAdapterclass:types/core-messenger.tswith Solana Snap messenger namespace + AssetsController / RemoteFeatureFlagController actionsendowment:messengertosnap.manifest.jsonAssetsProvider+RemoteFeatureFlagsProviderviagetMessengerinsnapContextAssetsServiceconstructor options (required for DI; not used for routing yet)@metamask/assets-controller,@metamask/messenger,@metamask/remote-feature-flag-controller,@metamask/snap-networks-utils--topological-devon rootyarn buildsosnap-networks-utilsbuilds before the snapSnap-owned
SnapAssetsAdapterremains the sole production read path.References
WPN-1476)Checklist