-
-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: integrating signature decoding api #4855
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to approve once the keyring-api
dependency is removed.
@@ -0,0 +1,8 @@ | |||
export const EthMethod = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor, this feels more like an enum as it's a fixed set of values to identify a type of something.
Which would also mean it could go in types.ts
.
But we can do this later since it's not exported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried that but it is giving build issues somehow.
## Explanation Signature controller update that add decoding api integration. ## References * Related to [#67890](MetaMask/MetaMask-planning#3553) ## Changelog ### `@metamask/signature-controller` - **ADDED**: Add isDecodeSignatureRequestEnabled to SignatureController constructor to be able to check if decoding api should be invoked for the signature ([#4903](#4903)) - **ADDED**: Integrating signature decoding api ([#4855](#4855)) ## Checklist - [X] I've updated the test suite for new or updated code as appropriate - [X] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [X] I've highlighted breaking changes using the "BREAKING" category above as appropriate - [X] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
Explanation
Integrate signature decoding api in signature-controller. When a permit request is received this api is called and the result is asynchronously updated into signature request.
References
Changelog
@metamask/signature-controller
Checklist