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.
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
Add
verifyContract
address normalization #309Add
verifyContract
address normalization #309Changes from all commits
c0920f5
06c86e2
d9fc14d
2ebe685
af2a8c2
a8e8e71
ba7ec73
5398f03
4baeb92
7c2e141
8da62e9
aa90200
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 17 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (16.x)
Check warning on line 17 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (18.x)
Check warning on line 17 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (20.x)
Check warning on line 43 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (16.x)
Check warning on line 43 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (18.x)
Check warning on line 43 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (20.x)
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.
Do we have a test for this?
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.
Done in af2a8c2
Check warning on line 57 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (16.x)
Check warning on line 57 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (18.x)
Check warning on line 57 in src/utils/normalize.ts
GitHub Actions / Build, lint, and test / Lint (20.x)
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.
[suggestion] could include tests for:
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.
As mentioned above (#309 (comment)), these test cases are already covered by the normalizer unit tests. I added this single eth_signTypedData_v3 test because it was missing from the wallet tests. Is there any advantage to adding essentially the same tests here as well?
Check warning on line 462 in src/wallet.ts
GitHub Actions / Build, lint, and test / Lint (16.x)
Check warning on line 462 in src/wallet.ts
GitHub Actions / Build, lint, and test / Lint (18.x)
Check warning on line 462 in src/wallet.ts
GitHub Actions / Build, lint, and test / Lint (20.x)