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
Currently, the test dapp only uses ethers.js for instantiating a provider. We need to also use web3.js, because many dapps use that exclusively. For us to properly test and QA MetaMask, we should test against the same tools that dapps use. Also, some functionality (e.g. batch transactions) are better supported by web3.js than ethers.
To start, let's just allow the test dapp to use web3 in place of ethers wherever it is currently used
add a radio button toggle somewhere on the top of the page. The options in the toggle should be "web3" and "ethers"
the toggle should default to ethers
if ethers is selected, the create token and deploy contract buttons should behave as they do today
if web3 is selected, create token and deploy contract should use web3 instead of the current "factories" created by the ethers provider, however the transactions created by the buttons should be the same
The text was updated successfully, but these errors were encountered:
Currently, the test dapp only uses ethers.js for instantiating a provider. We need to also use web3.js, because many dapps use that exclusively. For us to properly test and QA MetaMask, we should test against the same tools that dapps use. Also, some functionality (e.g. batch transactions) are better supported by web3.js than ethers.
To start, let's just allow the test dapp to use web3 in place of ethers wherever it is currently used
The text was updated successfully, but these errors were encountered: