Handle notifications
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
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.
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.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MetaMask/docusaurus-openrpc
-
team-wallet-api-platform
Difficulty 3/5 1-2 days Newbie friendliness 42/100
MetaMask/docusaurus-openrpc#71 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
team-wallet-api-platform
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in MetaMask/docusaurus-openrpc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openzim/mwoffliner#2933 ·
Maintainers usually reply within 1 day
-
Use the README category name for website links and submissionsPossibly taken @dajiaohuang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
birobirobiro/awesome-shadcn-ui#647 ·
Maintainers usually reply within 2 days
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Urigo/accounter-fullstack#4604 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day