We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It'd be cool if users can selectively enable checksum address caching. With this, it would basically be similar to Bob's https://github.com/BobTheBuidler/ypricemagic/blob/master/y/convert.py#L218-L239
And all checksumming will be cached.
For many users, this much caching is not desirable, it is application specific, that is why I am thinking it is something you can opt-in to.
config:
cache_checksum_address: True
and then have a fancy cache (similar to Bob's) that manages a cache of these addresses
No response
The text was updated successfully, but these errors were encountered:
APE-1889 Ability to enable checksum caching
Sorry, something went wrong.
No branches or pull requests
Describe
It'd be cool if users can selectively enable checksum address caching. With this, it would basically be similar to Bob's https://github.com/BobTheBuidler/ypricemagic/blob/master/y/convert.py#L218-L239
And all checksumming will be cached.
For many users, this much caching is not desirable, it is application specific, that is why I am thinking it is something you can opt-in to.
Specification
config:
and then have a fancy cache (similar to Bob's) that manages a cache of these addresses
Dependencies
No response
The text was updated successfully, but these errors were encountered: