-
Notifications
You must be signed in to change notification settings - Fork 41
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: added support for call value #142
Conversation
it('should handle msg.value', async () => { | ||
const value = BigNumber.from(123); | ||
await fake.connect(signer).receiveEmpty({ value }); | ||
expect(fake.receiveEmpty.getCall(0).value).to.eq(value); |
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.
why are we not using expect before?
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.
using should now
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.
looks great pal!
made some questions but ready to go 🚀
* feat: added support for call value (#142) * feat: arrays support for setVariable (#144) * feat: update ethereumjs vm and hardhat (#155) Co-authored-by: 0xOneTony <[email protected]>
* feat: added support for call value (#142) Added functionality: - `expect(myFake.myFunction).to.have.been.calledWithValue(1234);` - `expect(myFake.myFunction.getCall(0).value).to.eq(1);` * feat: arrays support for setVariable (#144) * feat: update ethereumjs vm and hardhat (#155) * fix: bug with usage of padNumHexSlotValue (#161) Co-authored-by: 0xOneTony <[email protected]>
Description
Adds full support for call
msg.value
, see changed documentation in order to see new implemented methodsMetadata