MetaMask / MetaMask/metamask-mobile
[NAVREDESIGN] Input Bar Component
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### **Description**
Create `Input Bar` component
### **Technical Details**
- This component is essentially an stylized extension of the existing `TextInput` component from React Native
- Props should probably extend that of a `TextInputProps`
- Usually this would be built in a stateless way, which means outside props control the value of what is shown but there may be benefits to building this in a stateful way, aka self managed state within the textinput itself. Up for discussion.
### **Acceptance Criteria**
- TBD
### **References**
- Figma - https://www.figma.com/file/qcwJHEEw5qyNru5mbFf6Oq/Nav-Redesign-Breakdown?node-id=114%3A3594
- ETA - 1 Day
Contributor guide
Research direction
Start by locating the existing TextInput component and review the linked Figma design for the Input Bar’s intended styling and behavior. Resolve whether the component is controlled or self-managed, then define acceptance criteria covering the TextInputProps-compatible API and visual match before implementing and verifying the component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100