Split components/bounty-detail/bounty-detail-submissions-card.tsx (411 lines) into smaller components

[Benjtalkshow]

components/bounty-detail/bounty-detail-submissions-card.tsx has grown to 411 lines and is now the largest component file in the bounty surface. It mixes:

• The card shell and header
• Per-submission row rendering with inline reviewer actions
• The review/approve/decline dialogs
• The IPFS link rendering and copy-to-clipboard helpers
• Status pills and tier badges

This makes it a constant merge-conflict surface and hard to reason about.

What to do

Split into per-responsibility files under components/bounty-detail/submissions/:

• submissions-card.tsx — the outer card shell, header, empty state, fetches and maps over submissions
• submission-row.tsx — single submission row with status pill, IPFS link, reviewer action buttons
• submission-review-dialogs.tsx — the approve/decline/request-revisions dialog wrappers (if they live in this file today)
• submission-helpers.ts — pure helpers like IPFS URL formatting, tier color mapping

Keep bounty-detail-submissions-card.tsx as a thin barrel re-export so callers don't break. Run pnpm tsc --noEmit and pnpm lint after each split.

Acceptance criteria

• No single file over 250 lines under components/bounty-detail/submissions/
• bounty-detail-submissions-card.tsx becomes a barrel or a thin shell that composes the new components
• All existing imports still resolve
• pnpm tsc --noEmit and pnpm lint pass
• No visual or behavioral change in the submissions card

Files

• components/bounty-detail/bounty-detail-submissions-card.tsx
• components/bounty-detail/submissions/ (new directory)

[linear]

BOU-307

[coderabbitai]

🔗 Related PRs

#17 - feat: Built BountyCard component with shadcn composition [merged]
#34 - feat: Implement API-driven bounty fetching and display with dedicated loading, empty, and error UI components. [merged]
#117 - feat: add frontend hooks for submission mutations [merged]
#165 - refactor: modularize BountiesPage and fix status filter bug (#127) [merged]
#201 - Feat/Dispute Resolution Workflow for Bounties [merged]
#236 - refactor: consolidate loading skeletons into shared ui/loading components [merged]
#241 - Split bounty-detail-sidebar-cta into three focused files [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!

[ezechinonyelumvivian-create]

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

Hi, I would love to work on this issue

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

[oscarj007]

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

I would love to take up this issue please

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

[felladaniel36-hash]

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

​Hi maintainer, I would love to work on this issue. I can get started on it right away. Could you please assign it to me? PLEASE!!!

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

[od-hunter]

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

Hi, can I be assigned this issue please? I’ve gone through the issue carefully and I’m up for the task, kindly assign me please

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

[drips-wave]

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

🧑‍💻 @od-hunter: 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 🌊