Add Storybook stories for QrShareDialog
Maintainers usually reply within 1 day
@CodePrincess360 is already working on this.
Since Oct 16, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start with the props interface in components/streams/qr-share-dialog.tsx, and use components/ui/badge.stories.tsx as the pattern for the new qr-share-dialog.stories.tsx next to it. Mock any hooks or providers the dialog calls so a story can render it with a sample stream. Done when the story appears in npm run storybook, npx tsc --noEmit reports nothing for the story file, and the open-with-sample-stream state has a story.
Written by the indexing model from the issue text.
Description
Description
QrShareDialog has no stories, so its states can't be reviewed in isolation.
Location
components/streams/qr-share-dialog.tsx. Stories live next to the component as *.stories.tsx (see components/ui/badge.stories.tsx).
Task
Add a *.stories.tsx covering:
- open with a sample 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
- 11h 47m
- Merged PRs (30d)
- 50
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 Storybook stories for SelectPossibly taken @Grace-CODE-D claimed this today. Opendocumentation frontend good first issue Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#967 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Add Storybook stories for FeeEstimateDialogPossibly taken @Grace-CODE-D claimed this today. Opendocumentation frontend good first issue Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FlowwStar/FlowStar#966 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Add Storybook stories for AccessibleUnlockAmountPossibly taken @Grace-CODE-D claimed this today. Opendocumentation frontend good first issue Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FlowwStar/FlowStar#965 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Move leftover hardcoded strings in the streams page into lib/copy/streams.tsPossibly taken @Grace-CODE-D claimed this today. Openfrontend good first issue Stellar Wave
Difficulty 1/5 Under an hour Newbie friendliness 85/100
FlowwStar/FlowStar#964 · 8 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Move leftover hardcoded strings in the stream detail page into lib/copy/stream-detail.tsPossibly taken @Userhorlie claimed this today. Openfrontend good first issue Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FlowwStar/FlowStar#963 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in FlowwStar/FlowStar
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 70/100
lingdojo/kana-dojo#32590 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bastani-inc/atomic#3703 ·
Maintainers usually reply within 1 day
-
backend bug difficulty: medium priority: medium reliability
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
trustflow-protocol/trustflow-backend#730 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
firecrawl/firecrawl-mcp-server#548 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day