You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR
The recent web3 release (beta 36) added a new ABI encoder which breaks some of my previous tests that use BigNumbers as function arguments (web3/web3.js#1936). The configurable version of web3 in embark.json only configures which version of web3 is used within the dapp, but not in the tests. In this case, and possibly more in the future it would be useful to allow configuration of the version of web3 used with embark test.
Extra Detail
Steps to reproduce
set version of web3 in embark.json
examine the version of the web3 object in your tests
Screenshots
Logs
Context (Environment)
OS: Mac OS 10.13.3
Embark Version: 3.2.2
Node Version: 10.7.0
NPM Version: 10.7.0
Questions?
Leave a comment on this issue! Make sure to use @ mentions if you want a specific person's attention!
The text was updated successfully, but these errors were encountered:
Overview
TL;DR
The recent web3 release (beta 36) added a new ABI encoder which breaks some of my previous tests that use BigNumbers as function arguments (web3/web3.js#1936). The configurable version of web3 in
embark.json
only configures which version of web3 is used within the dapp, but not in the tests. In this case, and possibly more in the future it would be useful to allow configuration of the version of web3 used withembark test
.Extra Detail
Steps to reproduce
embark.json
Screenshots
Logs
Context (Environment)
Questions?
The text was updated successfully, but these errors were encountered: