Add transaction type when normalising transaction object #1660
Conversation
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
| } | ||
| } | ||
|
|
||
| if (transaction?.type === '0x0') { |
Member
There was a problem hiding this comment.
Rather than hard coding this, should we not add an additional entry to NORMALIZERS above?
Contributor
Author
There was a problem hiding this comment.
Great feedback. Implemented here. Will be closing this PR
Contributor
Author
|
Closing this PR in favour of #1672 |
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
This PR includes transaction type if it's
0x0when normalising transactionsChangelog
@metamask/transaction-controllertransaction?.typewhen normalising transaction.Checklist