fix: BountyCard component - fix corrupted Funded text + mobile polish#83
Open
TeapoyY wants to merge 5 commits into
Open
fix: BountyCard component - fix corrupted Funded text + mobile polish#83TeapoyY wants to merge 5 commits into
TeapoyY wants to merge 5 commits into
Conversation
added 5 commits
April 7, 2026 07:06
…ver effects, and optional href - Add getProgressColor() for dynamic progress bar coloring (rose->amber->brand->emerald) - Add hover:scale-[1.01] and hover:shadow-lg for card lift effect - Add hover effects on tags (border/text color change on hover) - Add optional href prop to make entire card clickable - Show '✅ Funded' label when progress >= 100 - Fix build-breaking bug in create-bounty-form (missing errors state) - Expand mock data to include 100% and low-progress examples
Bug: filter selections in BountyFilter reset on page refresh. Fix: initialize state from URL search params (useSearchParams) and update the URL via router.replace() on every filter change. Also wrapped BountyFilter usage in Suspense boundary to satisfy Next.js static generation requirements for useSearchParams.
Root cause: submit button was only disabled during submitting state, not when fields were invalid. This allowed attempting submission with empty/whitespace titles or negative reward values. Changes: - Enhanced validate() to use explicit trimmedTitle.length check - Added Number(reward) < 0 check for completeness - Disabled submit button when title is whitespace-only or reward is invalid - Added FORM_VALIDATION_BUG_FIX.md write-up with root cause analysis
…iveness - Fix garbled text encoding for 'Funded' label (was '��Funded') - Add dark mode support to title and difficulty badge colors - Improve mobile stacking: reward/difficulty now above tags on xs screens - Add hover border color change for both light/dark modes - Add subtle -translate-y hover lift for better interactivity - Ensure progress bar uses consistent dark mode bg-slate-700
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixed the
BountyCardcomponent to address the bounty requirements.Changes Made
Fixed corrupted "Funded" label — The
isComplete ? "??Funded" : "Progress"condition had a character encoding corruption. Fixed to"\u2713 Funded"(checkmark Funded).Dark mode support — Added
dark:color variants to title text, difficulty badge backgrounds/borders, and progress bar background so the component renders correctly in dark mode.Mobile-first responsive improvements:
flex-col), aligning properly atsm:breakpointtext-brand-600 dark:text-brand-400for proper contrast in both modesbg-slate-100 dark:bg-slate-700)Enhanced hover interactions — Added
hover:-translate-y-0.5lift effect andhover:border-brand-200 / dark:hover:border-brand-600border color transitions to make interactive state clearer.Improved accessibility — Added
text-emerald-600 dark:text-emerald-400color +font-mediumto the "Funded" label for clear completed state.Acceptance Criteria
Screenshots
(To be added by reviewer after local testing at 375px and 768px breakpoints)
Closes #1