-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
@metamask/[email protected] #767
Conversation
f27ee2b
to
27cef8e
Compare
case SignTypedDataVersion.V4: | ||
return signTypedData_v4(privateKeyBuffer, { | ||
data: JSON.parse(messageParams.data as string), |
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.
These JSON.parse
calls were removed, but we still need this to be JSON data rather than a string
Some of the unit tests are failing here because of a mistake made in the typed message schema in |
The schema mistake has been fixed and published as [email protected] |
Is this something we need to get into the next release? I'm assuming no since this is still in draft, but just wanted to check. |
This was done in #914 |
Replaces
[email protected]
with@metamask/[email protected]
.This prevents some messages that appear to have been previously accepted from being signed, so this ought to be a breaking change.