Error on wallet_requestSnaps
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- api, documentation
Research direction
Open the linked wallet_requestSnaps documentation page and inspect the Send Request example, especially the parameter formatting. Reproduce the reported error, then verify that the corrected example sends successfully without changing the request's intended behavior.
Written by the indexing model from the issue text.
Description
Looks like there is an issue with the wallet_requestSnaps method (possibly with the format of the example)
From @Montoya
It’s this one: https://docs.metamask.io/wallet/reference/wallet_requestsnaps/
If you click Send Request you get an error, I think because the parameters are formatted wrong
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/api-specs
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
team-wallet-api-platform
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
team-wallet-api-platform
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
All issues in MetaMask/api-specs
Similar issues
-
Frontend good first issue P2-medium UI UX
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Deepak3699/Ai_Mentor#179 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
keyxmakerx/Chronicle#1061 ·
Maintainers usually reply within 1 day
-
Scrub the retired Kaizen target out of the deploy runbookPossibly taken @mcannonbrookes claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
atlassian-labs/roving-office#25 ·
Maintainers usually reply within 1 day
-
Remove the unused Forward Template editor from Messages settingsPossibly taken @atomantic claimed this today. Openarea:ui bug effort:low incomplete model:light plan planner:gpt-6-1-sol
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day