-
Notifications
You must be signed in to change notification settings - Fork 22
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
Provider refactor #61
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Adds much stricter typing to provider methods on both JSON RPC responses and requests
Uses Opaque type aliases microsoft/TypeScript#15807 (comment) to enforce that string types for responses and requests are properly verified. E.g there are specific opaque types for
DATA
Enforce that a string is ofDATA
type and variable lengthDATA_8B
EnforceDATA
type and is of 8 bytesDATA_20B
EnforceDATA
type and is of 20 bytesDATA_32B
EnforceDATA
type and is of 32 bytesDATA_256B
EnforceDATA
type and is of 256 bytesDATA_60B
EnforceDATA
type and is of 60 bytesQUANTITY
EnforceQUANTITY
type and is variable lengthSee https://github.com/ethereum/wiki/wiki/JSON-RPC#hex-value-encoding for more details
This forces the usage of typeguard functions for each of the above types, so that each guarding function takes an input of
string
and returns one of the opaque types above. The advantage of this is that when you see a type such asDATA_8B
, you know that it has already passed the string constraints ofDATA
type and is 8 bytes in length.Uses https://github.com/MyCryptoHQ/eth-rpc-types, which is modeled as closely as possible to the Ethereum JSON-RPC spec for each provider method.
Fixes the inheritance structure of the providers so that they inherit from abstract classes, avoiding the problem of typecasting methods to
any
or some classes not supporting as many methods as othersOpaque type usage example