-
Notifications
You must be signed in to change notification settings - Fork 2
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
Await .eventually
test matchers
#54
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Arr00 <13561405+arr00@users.noreply.github.com>
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.
This change is unrelated to the .eventually
part. @frangio and I agreed that the forbiden first char could cause bad issues (not being able to sign some ERC-712 objects).
We can reopen that discussion, but not in this PR.
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.
The tests currently have multiple cases that include the forbidden first characters.
Are you ok removing those cases?
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.
See d1b1289
Description
The
.eventually
chai matchers need to be awaited. From this, some issues raised. This PR fixes them