Parse hex numbers #270
Open
Parse hex numbers #270
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
giacomolicari
force-pushed
the
hex-parser
branch
from
5e0b809
to
a030979
Compare
added 3 commits
November 2, 2023 15:18
Signed-off-by: Giacomo Licari <giacomo@gnosis.io>
Signed-off-by: Giacomo Licari <giacomo@gnosis.io>
Signed-off-by: Giacomo Licari <giacomo@gnosis.io>
giacomolicari
force-pushed
the
hex-parser
branch
from
a030979
to
56f3fef
Compare
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.
This PR adds the ability for the scraper to convert hex numbers into float64.
Concrete example, if we have a JSON like:
where the key result is an hex representation of an integer, and we want that hex data to be correctly interpreted into a number, we would get it parsed from
0x1d55359to30757721.Also add a Dockerfile that builds the project.