MetaMask / MetaMask/metamask-mobile
Update react-native-share package
Open
Nobody has claimed this yet.
team-mobile-platform
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
What is this about?
- Update react-native-share library
- Make sure exportable scenarios are working
- Decide between json or txt file (currently txt)
- Understand if it's possible to download instead of only sharing via third apps
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
- Engineering (needed in most cases)
- Design
- Product
- QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- Security
- Legal
- Marketing
- Management (please specify)
- Other (please specify)
References
No response
Contributor 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.
Research direction
Start by locating the react-native-share integration and the export flows in the mobile app. Review how exports currently produce TXT files and how sharing through third-party apps works. Done means the package is updated, export scenarios work, and the JSON-versus-TXT and download behavior decisions are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100