Add Storybook stories for StreamTemplates
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- storybook, typescript
- Domain
- frontend
Research direction
Start with the props interface in components/streams/stream-templates.tsx, then copy the structure of components/ui/badge.stories.tsx for the new *.stories.tsx file next to it. Mock any hooks or providers the component calls so the default list story renders on its own. Done when a default list story shows in npm run storybook and npx tsc --noEmit reports no errors in the new file.
Written by the indexing model from the issue text.
Description
Description
StreamTemplates has no stories, so its states can't be reviewed in isolation.
Location
components/streams/stream-templates.tsx. Stories live next to the component as *.stories.tsx (see components/ui/badge.stories.tsx).
Task
Add a *.stories.tsx covering:
- default list
Use the component's real props (check its TypeScript props) and mock hooks/providers where needed.
Acceptance criteria
- Stories render in
npm run storybook -
npx tsc --noEmitreports no errors in the story file - Each listed state has a story
Good for contributors because
No app logic to change; a friendly way to learn the UI components.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 144
- Avg merge
- 7h 11m
- Merged PRs (30d)
- 37
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 @jdjioe5-cpu claimed this 14 days ago. Openfrontend good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
FlowwStar/FlowStar#1039 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Name the 15% fee buffer constant in fee-utils.tsPossibly taken @jdjioe5-cpu claimed this 14 days ago. Openfrontend 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 @jdjioe5-cpu claimed this 14 days 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
-
Add a timeout to the Friendbot request in TestnetFaucetBannerPossibly taken @jdjioe5-cpu claimed this 14 days ago. Openfrontend 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 @jdjioe5-cpu claimed this 14 days 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/langchainjs#12157 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
activescott/home-infra-k8s-flux#511 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
lingdojo/kana-dojo#33753 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
android:player
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
follow-up needs-triage S3: minor
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
manaflow-ai/cmux#38032 · 1 comment ·
Maintainers usually reply within 1 day