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
It would be handy to be able to leverage this package to create type hints for other packages that describe restrictions in abi types for different purposes, e.g. https://github.com/ApeWorX/eip712 where we currently use is_encodeable_type to parse a deferred type when describing an EIP-712 structured message like so:
classOrder(EIP712Message):
a: "address"# implicit validation using `eth_abi.is_encodeable_type`
It would be much nicer if all of the registered types were made available in mypy-compliant form to use for type checking code as follows:
frometh_abi.typesimportaddressclassOrder(EIP712Message):
a: address# explicit validation provided by eth_abi
Ideally, these types would work as aliases for int, Decimal, str, bytes, etc., doing the proper size and bounds checks as well (or at least allowing us to perform that validation easily) to make it easier to integrate this work into other libraries.
The text was updated successfully, but these errors were encountered:
It would be handy to be able to leverage this package to create type hints for other packages that describe restrictions in abi types for different purposes, e.g. https://github.com/ApeWorX/eip712 where we currently use
is_encodeable_type
to parse a deferred type when describing an EIP-712 structured message like so:It would be much nicer if all of the registered types were made available in mypy-compliant form to use for type checking code as follows:
Ideally, these types would work as aliases for
int
,Decimal
,str
,bytes
, etc., doing the proper size and bounds checks as well (or at least allowing us to perform that validation easily) to make it easier to integrate this work into other libraries.The text was updated successfully, but these errors were encountered: