Add Storybook stories for DashboardStats
Maintainers usually reply within 1 day
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, storybook, typescript
- Domain
- frontend
Research direction
Start with components/streams/dashboard-stats.tsx to read its TypeScript props and find any hooks or providers it uses. Copy the structure of components/ui/badge.stories.tsx and create a sibling dashboard-stats.stories.tsx with a with-data story and a skeleton story, mocking hooks or providers where needed. Done when the stories render 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
DashboardStats has no stories, so its states can't be reviewed in isolation.
Location
components/streams/dashboard-stats.tsx. Stories live next to the component as *.stories.tsx (see components/ui/badge.stories.tsx).
Task
Add a *.stories.tsx covering:
- with data
- skeleton
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 24m
- Merged PRs (30d)
- 55
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 8 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 8 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 8 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 8 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 8 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
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
🎙️ task - drop the raw `./node_modules/.bin/rhachet roles boot` line from bhuild's feedback templateOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ehmpathy/rhachet-roles-bhuild#639 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
redhat-developer/rhdh-plugin-export-overlays#4650 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 13 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
omdsh-dev/DSH-better-sidebar#1098 ·
Maintainers usually reply within 2 days