Extract hardcoded UI strings in ClearLocalData into lib/copy
Maintainers usually reply within 1 day
@Userhorlie is already working on this.
Since Oct 16, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with components/settings/clear-local-data.tsx and list every user-visible literal: labels, aria-label values, toast messages and placeholders. Follow the shape of lib/copy/dashboard.ts and lib/copy/streams.ts to create lib/copy/settings.ts, then import those strings into the component. Done when no literals remain in the component, the wording is unchanged, and the existing tests still pass after any needed import updates.
Written by the indexing model from the issue text.
Description
Description
Most pages now keep user-facing text in lib/copy/* modules, but ClearLocalData still hardcodes its labels, aria-labels, toasts and placeholders inline.
Location
components/settings/clear-local-data.tsx. Existing examples: lib/copy/dashboard.ts, lib/copy/streams.ts.
Task
Move every user-visible string into lib/copy/settings.ts and import it in the component. Keep wording identical.
Acceptance criteria
- No user-visible string literals remain in the component
- Existing tests still pass (update string imports in tests if needed)
- UI is unchanged
Good for contributors because
Mechanical refactor following an established pattern.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 144
- Avg merge
- 9h 24m
- Merged PRs (30d)
- 72
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from FlowwStar/FlowStar
-
Remove unused formatFee() from fee-utils.tsPossibly taken @jiangyuer018 claimed this 1 day ago. Openfrontend good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
FlowwStar/FlowStar#1039 · 3 comments ·
Maintainers usually reply within 1 day
-
frontend good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Add a timeout to the XLM price fetch in use-token-pricePossibly taken @Dekah101 claimed this 1 day ago. Openfrontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
FlowwStar/FlowStar#1037 · 1 comment ·
Maintainers usually reply within 1 day
-
frontend good first issue ux
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FlowwStar/FlowStar#1036 · 1 comment ·
Maintainers usually reply within 1 day
-
Add a request timeout to Horizon fetches in lib/stellar.tsPossibly taken @Ikechukwu-Patrick claimed this 1 day ago. Openfrontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#1035 · 1 comment ·
Maintainers usually reply within 1 day
All issues in FlowwStar/FlowStar
Similar issues
-
check:failed streams:edit
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
iptv-org/iptv#55901 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
package:ios ships XCFrameworks with absolute symlinks, which SwiftPM refuses to extractPossibly taken @cusnirvladislav claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
callstackincubator/rock#740 ·
-
S: triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
area:workflow bug ready-for-human
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fil-donadoni/tolaria#6108 ·
Maintainers usually reply within 1 day