Add confirmed-in component, show ETA for proposed reimbursements #210

Merged
raucao merged 11 commits from feature/confirmation-eta into master 2023-01-15 04:36:43 +00:00
raucao commented 2023-01-11 06:21:58 +00:00 (Migrated from github.com)

Adds a generic component for showing confirmation ETAs for any item, and adds the ETA to proposed reimbursements in the UI.

Also adds an event listener for new blocks, which updates the currentBlock number, so that all models, as well as the UI, can auto-update.

Screenshot from 2023-01-11 14-18-50

Adds a generic component for showing confirmation ETAs for any item, and adds the ETA to proposed reimbursements in the UI. Also adds an event listener for new blocks, which updates the `currentBlock` number, so that all models, as well as the UI, can auto-update. ![Screenshot from 2023-01-11 14-18-50](https://user-images.githubusercontent.com/842/211732255-44671f5d-7b67-4cc8-8e3e-d5dc7b42e677.png)
galfert (Migrated from github.com) reviewed 2023-01-11 06:21:58 +00:00
fsmanuel (Migrated from github.com) reviewed 2023-01-11 06:21:58 +00:00
bumi (Migrated from github.com) approved these changes 2023-01-13 20:34:42 +00:00
bumi (Migrated from github.com) left a comment

could not test it, but looks good.

could not test it, but looks good.
raucao commented 2023-01-14 04:16:51 +00:00 (Migrated from github.com)

Cool, thanks.

What's the problem with testing? Should really just be npm start, without any wild dependencies (except for a local IPFS daemon/gateway running).

Btw, I opened #211 against this PR yesterday in order to avoid conflicts, so it would be good to merge that first.

Cool, thanks. What's the problem with testing? Should really just be `npm start`, without any wild dependencies (except for a local IPFS daemon/gateway running). Btw, I opened #211 against this PR yesterday in order to avoid conflicts, so it would be good to merge that first.
Sign in to join this conversation.