Linking Transaction History from API to Redux

[bkawk]

Linking the front end to the API

• Check and possibly amend the naming of the socket connection/subscription with the API to all in line with the specification exactly.

• Create and maintain a redux array with all transactions in.

• When a new transaction is created and a recipe is returned push the transaction into this array with a status of pending.

• Listen to txHistoryChanged, on change update redux with the changes

• If txHistoryChanged retunes an item that is in the redux array, delete it from redux first then insert it to stop mutations.

Dependencies

• API returns data as specified
• Api Subscript is as named and functioning
• Comments answering on SwarmCityConceptIssue #2

Time Estimate

9 hours

[xardass]

Hi Will, I added a redux property on branch #675_txhistory-frontend: txHistory. Up to you if you decide to keep it or not.

[sponnet]

Note : You can now link issues to epics in another repo ( an undiscovered feature of ZenHub ) I linked this issue to its corresponding epic & changed its title. This issue will be followed-up in the PM board : https://github.com/swarmcity/SwarmCityPM#boards

[sponnet]

amount of confirmations is not shown in this iteration. ( not part of the epic ). This means that when a Tx history comes in - it is shown as is. The only state change can be from pending to confirmed.

[BvL13]

@eduadiez and @xardass can you solve this issue?

[eduadiez]

This is a frontend job so I've assigned to @xardass

[xardass]

Thanks, I can take this