[496] Features: Push notification, Incoming Transaction, Websockets#1739
[496] Features: Push notification, Incoming Transaction, Websockets#1739ifaouibadi wants to merge 9 commits intodevelopfrom
Conversation
|
Deployed to features-push-notification.wallet.z52da5wt.xyz, artifacts |
59d59af to
1da6eac
Compare
25a4750 to
935e243
Compare
88e16c6 to
3ae242a
Compare
3ae242a to
80dc992
Compare
|
I remember @thepiwo once said we will introduce a web socket for multisig backend too to detect new multisig vaults. |
|
I started work on websockets for the ga-multisig backend, but we never followed up with an actual plan on integration, so I abandoned the approach for the time aeternity/ga-multisig-backend@515b598 let's have a meeting to pick it up again |
This is important to optimize the performance of the SH wallet, especially to eliminate polling to the multisig backend. Let's talk soon ✌️ |
Improved network unsubscribe from previous when it's been changed
it's not a good idea to listen for all networks been added in the app as it can cause notifications duplicate or receiving unexpected notification from non active network |
Fine. |
|
I suggest to add a redirect from transaction notification to open details of this transaction . |
src/popup/utils/constants.ts
Outdated
There was a problem hiding this comment.
This is actually not an channel name. Also Object is already used in the IMiddlewareWebSocketSubscriptionMessage payload prop.
There was a problem hiding this comment.
it's a channel name :D https://github.com/aeternity/ae_mdw#publishing-message-format
used to subscribe for specific address
There was a problem hiding this comment.
Changes done in this file are not necessary as non of the files are using them.
subhod-i
left a comment
There was a problem hiding this comment.
We will have a re-review. Multiple updates
No description provided.