Move leftover hardcoded strings in the create form into lib/copy/create-form.ts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nextjs, typescript
- Domain
- frontend
Research direction
Start by comparing app/app/create/create-form.tsx with the keys already defined in lib/copy/create-form.ts, then grep the form file for quoted user-visible sentences, including toast messages and labels. Move each remaining literal into the copy file under a key that matches the existing naming, and import it from the component. Done when the grep finds no user-visible literals left in the form and the existing tests for the create form still pass.
Written by the indexing model from the issue text.
Description
Description
app/app/create/create-form.tsx was migrated to lib/copy/create-form.ts, but a few strings were missed, e.g. a handful of labels and toast messages.
Location
app/app/create/create-form.tsx; lib/copy/create-form.ts.
Task
Find the remaining user-visible literals (grep for quoted sentences) and move them into lib/copy/create-form.ts.
Acceptance criteria
- No user-visible string literals remain
- Tests still pass
Good for contributors because
Small follow-up to an existing refactor.
- 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