Refactor TermsOfUse page component
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 427
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
💡 Summary
File: frontend/src/pages/TermsOfUse/TermsOfUse.tsx
The TermsOfUse page component contains a mixture of logic, content, and style. It needs to be broken down in to smaller, more focused subcomponents.
Motivation and context
Cleans up the code so that it is easier to evaluate and manage.
Acceptance criteria
- Style is moved into it's own file
- All in-line style is moved out of JSX into css classes
- All logic is moved from JSX into variables defined by typescript
- All areas of concern are broken off into subcomponents
- Markup represents what is visually in the page
Contributor guide
No contributing guide indexed for this repository
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 reading frontend/src/pages/TermsOfUse/TermsOfUse.tsx to identify the current logic, content, inline styles, and visual areas. Done means styles are in a separate file, JSX uses CSS classes, logic is represented by TypeScript variables, and distinct concerns are separated into subcomponents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100