Extract hardcoded UI strings in StreamTimeline into lib/copy
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, typescript
- Domain
- frontend
Research direction
Start with components/streams/stream-timeline.tsx and list every visible label, aria-label, toast and placeholder string. Compare with lib/copy/streams.ts and lib/copy/dashboard.ts to match the existing export shape, then create lib/copy/stream-detail.ts and import from it. Run the existing tests for the stream timeline and update any string imports they need. Done when no user-facing literals remain in the component, tests pass, and the rendered text is unchanged.
Written by the indexing model from the issue text.
Description
Description
Most pages now keep user-facing text in lib/copy/* modules, but StreamTimeline still hardcodes its labels, aria-labels, toasts and placeholders inline.
Location
components/streams/stream-timeline.tsx. Existing examples: lib/copy/dashboard.ts, lib/copy/streams.ts.
Task
Move every user-visible string into lib/copy/stream-detail.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
- 13h 50m
- Merged PRs (30d)
- 41
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
-
Add a Storybook section to CONTRIBUTING.mdPossibly taken @ChanakyaG2004 claimed this 1 day ago. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#995 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation good first issue testing
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
FlowwStar/FlowStar#994 · 2 comments ·
Maintainers usually reply within 1 day
-
Document how Playwright visual baselines are generatedPossibly taken @minutechreview claimed this 1 day ago. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FlowwStar/FlowStar#993 · 2 comments ·
Maintainers usually reply within 1 day
-
devops good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
devops documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
FlowwStar/FlowStar#991 · 2 comments ·
Maintainers usually reply within 1 day
All issues in FlowwStar/FlowStar
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melgarafael/DeskcommCRM#3000 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
callstackincubator/simlock#639 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
aws/agentcore-cli#2606 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 7 days
-
ai-driven-qa bug Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day