MetaMask/metamask-extension

Replace deprecated TextField component with TextField from the component-library

Open

#20483 opened on Aug 16, 2023

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (11,014 stars) (4,848 forks)batch import
good first issueteam-design-system

Description

Description

Currently, the extension is using an outdated TextField component, which needs to be replaced with the new TextField component.

This is a massive undertaking by itself and creating a single PR would be too large. Smaller PRs can be submitted against this issue to ensure easier review and gradual improvements. It also means that this issue will not be assigned to a single engineer

Technical Details

  • Replace instances of TextField component (ui/components/ui/text-field/text-field.component.js) with TextField component (ui/components/component-library/text-field/text-field.js)
  • Component APIs are slightly different so ensure all props have been migrated appropriately
  • Ensure there are no visual or functional regressions

Acceptance Criteria

  • Instances of TextField component are completely replaced with the new TextField component
  • The component APIs are updated to reflect the changes in the new `TextField`` component and there is no functional changes or visual regression
  • Each Pull Request (PR) should include no more than 3 files
  • The code changes should pass Jest tests, linting, and Storybook without any errors.
  • The PR must include before and after screenshots of the UI to ensure there are no visual regressions.

If the acceptance criteria is not met, PRs may be closed.

Difficulty: Intermediate

Good first issue for: External contributors who are familiar with running the extension locally, have knowledge of React, component props, Jest tests, linting, and Storybook, and want to contribute to improving the cohesiveness of UI in the extension

Contributor guide

Tech stack
javascriptreactjeststorybook
Domain
frontendtesting
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
React knowledgeJest testingStorybookMetaMask extension setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Start by comparing the APIs of the old TextField (ui/components/ui/text field/text field.component.js) and the new TextField (ui/components/component library/text field/text field.js). Identify all instances of the old component across the codebase using grep. For each instance, map the props to the new API carefully, noting any differences. After making changes, run Jest tests and Storybook to ensure no regressions. Include before and after screenshots in the PR as required.