Add EOS address methods to SDK#395
Conversation
Codecov Report
@@ Coverage Diff @@
## master #395 +/- ##
===========================================
+ Coverage 38.4% 60.79% +22.39%
===========================================
Files 71 74 +3
Lines 9682 9812 +130
Branches 2121 2139 +18
===========================================
+ Hits 3718 5965 +2247
+ Misses 5327 2913 -2414
- Partials 637 934 +297
Continue to review full report at Codecov.
|
tylerlevine
left a comment
There was a problem hiding this comment.
looks pretty good - quite similar to xlm! Just a few nits to clean up
There was a problem hiding this comment.
I don't think you need the = function part there
There was a problem hiding this comment.
I don't think you need the = function part there
There was a problem hiding this comment.
Should throw an InvalidAddressError since we already have that error type defined
There was a problem hiding this comment.
I think these Errors can be InvalidAddressErrors also
There was a problem hiding this comment.
Isn't this testing the same thing as the test above, except we do the crypto.randomBytes() before we call the function? If the intention is to make sure we deterministically generate a keypair from a seed, then it might make more sense to use a static seed instead of a random one and make sure you get the key you're expecting.
There was a problem hiding this comment.
yes, it makes more sense. Done.
marktoda
left a comment
There was a problem hiding this comment.
Ah nice! Thanks for doing this. I think we copied a bit of work with CT-393-eos-sdk branch but all good, ill just merge that into this one as this is more fleshed out. Everything looks good to me, will let tyler take over
b7b5e9f to
d65f5d1
Compare
Yes, I used your branch as a base. I only left out the logic for signing, actually. |
tylerlevine
left a comment
There was a problem hiding this comment.
One more thing, rest looks good
There was a problem hiding this comment.
if the spec is less than 12, then this condition is wrong and should be >=. What should the behavior be if the address is exactly 12 characters?
There was a problem hiding this comment.
It's up to 12 characters. Fixed the comment
d65f5d1 to
1e7ccf4
Compare
1e7ccf4 to
cccdffc
Compare
cccdffc to
682d3f4
Compare
Add EOS class with methods for address handling required by the client