Protect internals of the provider classes using hash names
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api
Research direction
Start by locating the provider classes in the TypeScript repository and reading how snaps-monorepo currently wraps the Ethereum provider in a Proxy. Identify the internal fields that require protection and review the provider tests, if present. Done means those internals are protected directly and the Proxy workaround is no longer needed.
Written by the indexing model from the issue text.
Description
Currently in snaps-monorepo we wrap the Ethereum provider in a Proxy, to prevent access to internal fields. A better alternative would be to protect these fields in the first place using hash names, which are not accessible in any way.
- Dominant language
- TypeScript
- Stars
- 268
- Forks
- 130
- 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/providers
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Remove unnecessary export entriesPossibly taken @ZayanKhan-12 claimed this 62 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in MetaMask/providers
Similar issues
-
failed-test failure:ai-fixable failure:test-needs-update Team:One Workflow
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
elastic/kibana#295360 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ehmpathy/rhachet-roles-bhrain#586 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OHDSI/Data2Evidence#3496 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
apache/rocketmq-dashboard#5594 ·
Maintainers usually reply within 3 days
-
react-doctor severity:warning tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 82/100
digidem/comapeo-cloud-app#418 ·
Maintainers usually reply within 1 day