Add Storybook stories for DownloadReceiptButton
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- storybook, typescript
- Domain
- frontend
Research direction
Read the props type in components/streams/download-receipt-button.tsx, then copy the structure of components/ui/badge.stories.tsx. Add a sibling download-receipt-button.stories.tsx with one story for an active stream and one for a completed stream, mocking any hooks or providers the component uses. Done when both stories appear under 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
DownloadReceiptButton has no stories, so its states can't be reviewed in isolation.
Location
components/streams/download-receipt-button.tsx. Stories live next to the component as *.stories.tsx (see components/ui/badge.stories.tsx).
Task
Add a *.stories.tsx covering:
- active stream
- completed stream
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
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
aws/agentcore-cli#2606 ·
Maintainers usually reply within 1 day
-
ai-driven-qa bug Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
linagora/twake-mail-admin#301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
anomalyco/opencode#56038 · 1 comment ·
Maintainers usually reply within 1 day