-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Conversation
Yes, this is a side effect of #3900. Sorry, this one is my fault; I should have made sure the jsapi wasn't broken. |
@rphmeier No worries, it's a small fix ! |
@@ -129,12 +129,31 @@ export function outNumber (number) { | |||
return new BigNumber(number || 0); | |||
} | |||
|
|||
export function outPeer (peer) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would really have liked tests for this. (API is close to full coverage, not for the sake of coverage, but rather since it is such a critical piece.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Especially since what we are actually fixing is a bug - for those case need to have the original (doesn't break it) plus the new (this used to break) case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the tests
* Fix wrong output format of peers * Add outPeer tests
It seems that from 1.6 the
parity_netPeers
RPC call could return peers withnull
protocol. The UI wouldn't properly work.