Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add Storybook stories for ConnectWalletButton

Closed Beginner friendly
#975 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Crypto-Oracle001 is already working on this.

Since Oct 16, 2026.

  • #1001 by @Crypto-Oracle001 — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
storybook, typescript
Domain
frontend

Research direction

Start with the TypeScript props in components/layout/connect-wallet-button.tsx, then copy the structure of components/ui/badge.stories.tsx for the new *.stories.tsx file. Mock whatever hook or provider supplies the wallet state so the disconnected, connected and reconnecting stories can be set up without app logic. Done when all three stories render under npm run storybook and npx tsc --noEmit reports no errors in the story file.

Written by the indexing model from the issue text.

Description

documentation frontend good first issue

Description

ConnectWalletButton has no stories, so its states can't be reviewed in isolation.

Location

components/layout/connect-wallet-button.tsx. Stories live next to the component as *.stories.tsx (see components/ui/badge.stories.tsx).

Task

Add a *.stories.tsx covering:

  • disconnected
  • connected
  • reconnecting

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 --noEmit reports 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FlowwStar/FlowStar

All issues in FlowwStar/FlowStar

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.