fix: replace computed Network enum initialisers with string literals - #101
Merged
Conversation
hmalik88
marked this pull request as ready for review
August 4, 2026 04:03
Contributor
Author
|
@metamaskbot publish-preview |
Contributor
|
Preview builds have been published. Learn how to use preview builds in other projects. Expand for full list of packages and versions. |
ccharly
approved these changes
Aug 4, 2026
ccharly
left a comment
Contributor
There was a problem hiding this comment.
We should really ban enum 🥹
hmalik88
enabled auto-merge
August 4, 2026 09:25
ulissesferreira
approved these changes
Aug 4, 2026
2 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
Networkenum members were initialised fromTrxScope.Mainnet / .Nile / .Shasta(a regular, non-const enum). TypeScript compiles any enum with computed initialisers using the bidirectional numeric-enum pattern, soObject.values(Network)returned 6 values: the 3 CAIP-2 scope IDs plus their reverse-mapped human-readable names ("Mainnet","Nile","Shasta").bip44:discoveriteratesObject.values(Network)to check on-chain activity on every scope. When it reached"Mainnet",checkAddressActivitycalledgetTransactionInfoByAddress("Mainnet", addr), which threw"No client configured for network: Mainnet", causingPromise.allto reject and every discovery attempt to silently return[].Object.values(Network)now returns only the 3 scope IDs.Test plan
yarn workspace @metamask/tron-wallet-snap run build— no type errorsyarn workspace @metamask/tron-wallet-snap run test— all tests passdiscovers Tron accounts through Account 5e2e test inmetamask-extensionand confirm it passesReferences
N/A
Checklist