Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

[FIX] fix parsing incoming trust lines #2154

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

darkdarkdragon
Copy link
Contributor

JsonRewriter: correctly parse limit, limit_peer and noRipple properties of
incoming trust line transaction
Trust Tab: correctly show "Rippling" field for incoming trust lines

@vhpoet
Copy link
Contributor

vhpoet commented Jan 30, 2015

show Rippling for incoming trust lines? where do you show a rippling for incomings?

@darkdarkdragon
Copy link
Contributor Author

develop-fix-trust-line-parsing-1

  1. Rippling incorrectly shown for incoming trustlines
  2. For just-created incoming trust line limit is not in place - it must be in "Min"
  3. Edit turned on for just created trust line - it is unrecognized as incoming.

@vhpoet
Copy link
Contributor

vhpoet commented Feb 2, 2015

Does this mean the "Rippling" is sometimes showing the incoming rippling and sometimes the outgoing one?

effect.limit = ripple.Amount.from_json(viewHigh ? high : low);
effect.limit_peer = ripple.Amount.from_json(viewHigh ? low : high);

effect.type = obj.transaction.type == 'trusting' ? 'trust_create_local' : 'trust_create_remote';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could use === here.

JsonRewriter: correctly parse limit, limit_peer and noRipple properties of
incoming trust line transaction
Trust Tab: correctly show "Rippling" field for incoming trust lines
@darkdarkdragon
Copy link
Contributor Author

@vhpoet It is one table for all trust lines - incoming and outgoing. But "Rippling" column shows incorrect data for incoming trustilines

@coveralls
Copy link

Coverage Status

Coverage remained the same at 68.75% when pulling 7de0e1b on darkdarkdragon:develop-fix-trust-line-parsing into 70f67ba on ripple:develop.

@vhpoet vhpoet force-pushed the develop branch 2 times, most recently from f095e33 to 9768d18 Compare February 24, 2015 19:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants