MetaMask / MetaMask/metamask-mobile

Convert ExpandedMessage into functional component

Open
#5,566 1 comment 0 reactions 0 assignees View on GitHub
area-signatures team-confirmations-planning type-pinned type-tech-debt
Dominant language
TypeScript
Stars
3k
Forks
1.7k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

### **Description**

Convert ExpandedMessage into functional component:

https://github.com/MetaMask/metamask-mobile/blob/18dc20b8cc9f3f0707f5eb04f2ac88ee320c93bb/app/components/UI/SignatureRequest/ExpandedMessage/index.js

### **Acceptance Criteria**
- Signature request functionality continues to work as it is currently
- Use of deprecated react api is removed

### **References**
https://docs.google.com/document/d/19xKY4e07UThOa1jsDQA8pjsNLUBRn39EdUbaFpz3OR0/edit?usp=sharing

Contributor guide

Open the contributing guide

Research direction

Open app/components/UI/SignatureRequest/ExpandedMessage/index.js and review how ExpandedMessage currently handles signature request behavior and deprecated React APIs. Convert the component while preserving its existing functionality, then verify that signature requests continue to work and the deprecated API is no longer used.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react, react-native
Domain
frontend, mobile
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.