MetaMask / MetaMask/docusaurus-openrpc
Handle notifications
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Not sure how we'd handle this but would be nice to show the user `notifications` coming across the wire.
for metamask `accountChanged` for example is a notification that just comes across the wire.
also `eth_subscribe` kicks off notifications that come back with a notificationId via `eth_subscription` notification.
We need to handle these and show them to the user somehow.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating how the interactive documentation receives and displays messages, then investigate the accountChanged and eth_subscription notification flows. Done should include a defined user-facing treatment for both unsolicited notifications and subscription notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100