Closed albrow closed 6 years ago
Please remove yarn.lock
@fanatid Done
@fanatid Could we merge it and publish a new version? Are we waiting on other reviewers?
@LogvinovLeon I'm not in npm package owners. Ping @holgerd77
@holgerd77 is on vacation starting from Saturday for 2 weeks. I pinged him already. No worries. It's not urgent. We're just using our fork for now.
@holgerd77 are you back from vacation? ;) Would be great if we could get this merged and published.
@fabioberger Yes (was great! :-)), I'll probably find some time to have a look into this tomorrow and hopefully directly release!
Ok, just published the new release v1.3.5
.
Thanks @holgerd77!
The documentation for
FakeTransaction.hash
shows thatincludeSignature
is supposed to betrue
by default. However, this is not the case and the implementation treatsincludeSignature
asfalse
by default.This was causing us issues with Ganache, where we were seeing the same transaction hash for different transactions (because they were all using a
FakeTransaction
without overriding the signature). It looks like #81 was designed to fix this issue, but since Ganache does not explicitly provide the argumenttrue
toFakeTransaction.hash
, the issue was still occurring.I believe the implementation should match the documentation and
includeSignature
should betrue
by default. Doing so also fixes the duplicate transaction hashes we were seeing in Ganache.