Skip to content

Conversation

@eswan18
Copy link
Owner

@eswan18 eswan18 commented Feb 5, 2026

Summary

  • Add PropStatusBadge component that displays prop lifecycle status (open, closed, resolved-yes, resolved-no)
  • Create lib/prop-status.ts with helper functions to compute status from prop dates and resolution
  • Replace previous resolution-only badges with more informative status indicators
  • Add Storybook stories for visual testing and documentation

Test plan

  • Run npm run test - all 159 tests pass
  • Run npm run lint - no errors
  • Run npx tsc --noEmit - no type errors
  • Run npm run storybook and verify PropStatusBadge stories render correctly
  • Manual test on /competitions/[id] to see badges on forecast cards
  • Manual test on /props/[id] to see badge in header

🤖 Generated with Claude Code

Introduce a reusable badge component that displays prop lifecycle status
(open, closed, resolved-yes, resolved-no) based on deadlines and resolution.
This replaces the previous resolution-only badges with more informative
status indicators that show whether props are still accepting forecasts.

- Add lib/prop-status.ts with getPropStatus helper function
- Add PropStatusBadge component with colored variants
- Add Storybook stories for visual testing
- Integrate into forecast cards and prop detail page header

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Feb 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
forecasting Ready Ready Preview, Comment Feb 5, 2026 4:10am

@eswan18 eswan18 merged commit 93cd3bc into main Feb 5, 2026
3 checks passed
@eswan18 eswan18 deleted the feat/prop-status-badges branch February 5, 2026 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant