Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Use listener instead of resolveMap and rejectMap

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
react-native, typescript
Domain
mobile-dev

Research direction

No file, entry point, test, or implementation context is provided. Start by locating resolveMap and rejectMap in the TypeScript React Native code, then trace how their results are consumed before deciding how listener-based handling should replace them. Done means the old maps are no longer needed and existing behavior remains covered by tests.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
TypeScript
Stars
5
Forks
2
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/react-native-mpc-core-kit

All issues in MetaMask/react-native-mpc-core-kit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.