Update AbstractProvider and contract.methods TS definitions #3521
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
release/1.2.8
branchAddresses tsc compilation errors generated while E2E testing 1.2.8 release vs. gnosis/dex-react as noted in this review comment.
methods
andcall
#3454any
but that violates a TS lint rule about "union with any"connected
property to AbstractProviderAs discussed in chat, the error thrown by the AbstractProvider definition is a little confusing.
The problematic code can be found here and looks like:
All the other Web3 providers have a connected property. Idk if the change in this PR is the right solution (...it squashes the tsc complaint though).
Type of change
Checklist: