f94f98e0f3
(1) Due to IAPI/commerce query limit, and also to not pollute the wallet with infinite chargeCodes, we'll only show the last 10 swaps. Beamer mentioned that it's possible to tracked back the past chargeCodes of the user, and potential provide a `list` endpoint to handle disputes. (2) If a user explicitly removed an entry, don't repopulate that entry even if websocket returned an updated status for it. While it might be useful to handle accidental removals, it looks weird when the list gets repopulated with 'Expired' entries. (3) Add sanitization when repopulating the chargeCodes from the wallet data (i.e. remove 'null' entries). (4) Always repopulate the list per wallet data so every instance looks the same. |
||
|---|---|---|
| .. | ||
| actions | ||
| reducers | ||
| selectors | ||