Skip to content

Allow to parse uppercase 0X#842

Merged
erikzhang merged 2 commits intoneo-project:masterfrom
shargon:uppercase
Jun 19, 2019
Merged

Allow to parse uppercase 0X#842
erikzhang merged 2 commits intoneo-project:masterfrom
shargon:uppercase

Conversation

@shargon
Copy link
Copy Markdown
Member

@shargon shargon commented Jun 18, 2019

0x01 and 0X01 should be valid

@codecov-io
Copy link
Copy Markdown

codecov-io commented Jun 18, 2019

Codecov Report

Merging #842 into master will not change coverage.
The diff coverage is 25%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #842   +/-   ##
=======================================
  Coverage   38.39%   38.39%           
=======================================
  Files         176      176           
  Lines       12465    12465           
=======================================
  Hits         4786     4786           
  Misses       7679     7679
Impacted Files Coverage Δ
neo/UInt256.cs 54.54% <0%> (ø) ⬆️
neo/UInt160.cs 55.84% <50%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d63f0ed...38c642a. Read the comment docs.

@igormcoelho
Copy link
Copy Markdown
Contributor

igormcoelho commented Jun 18, 2019

0x prefix means bigendian (worldwide standard and Neo convention). So, as long as it is parsed the same way it is printed tostring, its fine.
example:
parse 010203. Tostring 0x030201
parse 0x010203 tostring 0x010203

This is why.we need to fix neovm json tests... it is using 0x but not bigendian (see scripthash field)... I didnf say before, but now its time 😂

@erikzhang erikzhang merged commit 70bf2f5 into neo-project:master Jun 19, 2019
@erikzhang erikzhang deleted the uppercase branch June 19, 2019 05:45
Thacryba pushed a commit to simplitech/neo that referenced this pull request Feb 17, 2020
Tommo-L pushed a commit to Tommo-L/neo that referenced this pull request Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants