Remove the as unknown as Bounty cast in bounty-card.tsx slot count

[Benjtalkshow]

components/bounty/bounty-card.tsx:232 reads the slot count with an ad-hoc cast:

{(bounty as unknown as Bounty).totalSlotsOccupied ?? 0} / {(bounty as unknown as Bounty).maxSlots ?? 5} slots

PR #263 added totalSlotsOccupied?: number | null and maxSlots?: number | null as optional fields on the Bounty interface. The cast is no longer needed.

What to do

• Drop the two (bounty as unknown as Bounty) casts on line 232
• If bounty is typed as BountyFieldsFragment, widen the prop type to BountyFieldsFragment & Partial<Bounty> to follow the same pattern used in bounty-detail-sidebar-cta.tsx and bounty-detail-mobile-cta.tsx
• Confirm pnpm tsc --noEmit stays clean

Acceptance criteria

• The two casts on bounty-card.tsx:232 are gone
• No (bounty as unknown as Bounty) or (bounty as { ... }) casts remain in components/bounty/
• pnpm tsc --noEmit and pnpm lint pass

Files

• components/bounty/bounty-card.tsx

[linear]

BOU-295

[Emmo00]

@Emmo00 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emmo00 to this issue.

[coderabbitai]

🔗 Related PRs

#178 - Feat/competition bounty flow [merged]
#241 - Split bounty-detail-sidebar-cta into three focused files [merged]
#251 - Implement Apply for Slot on Multi-Winner Milestone bounties [merged]
#252 - fix(apply-for-slot): lint and import cleanup from PR #251 [merged]
#263 - fix(#211): extend Bounty type with optional UI fields, remove ad-hoc … [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[leocagli]

Hi! I'd like to remove the as unknown as Bounty cast in bounty-card.tsx by fixing the type properly. This improves type safety without any runtime behavior change. Could I be assigned?

[shogun444]

@shogun444 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I'd like to work on this issue.

My plan is to remove the unnecessary as unknown as Bounty casts from bounty-card.tsx now that totalSlotsOccupied and maxSlots are already part of the Bounty interface. If needed, I'll align the prop typing with the existing pattern used in bounty-detail-sidebar-cta.tsx and bounty-detail-mobile-cta.tsx to keep the component type-safe without unsafe casts.

I'll also verify there are no remaining Bounty casts under components/bounty/ and run pnpm tsc --noEmit and pnpm lint to ensure there are no regressions.

Portfolio: https://portfolio-amber-one-v8ggyhsjyr.vercel.app/

ETA - 1 hour

ℹ️ Repo Maintainers: To accept this application, review their application or assign @shogun444 to this issue.

[abimbolaalabi]

@abimbolaalabi has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer! I’m interested in contributing to this task and can ensure timely delivery with clean implementation. I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it. Thank You!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abimbolaalabi to this issue.

[drips-wave]

Congratulations, @abimbolaalabi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @abimbolaalabi: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊