Surface partial-load failures on the dashboard

[Jaydbrown]

failedCount is computed but not shown. Add an inline banner: "N streams couldn't be loaded — retry".

[ZacLou]

I'd like to work on this issue. I have relevant experience with this tech stack and can deliver a clean, well-tested PR. I can submit within 1-2 days.

[Ranjeet2063]

Hi maintainers, I would love to take up this issue.

I am a senior Web3 frontend engineer (#1 contributor on Mova Store with 28 successfully merged PRs), specializing in Next.js, React, TypeScript, Tailwind CSS, and Freighter/Stellar wallet integrations.

🎯 Technical Execution Plan for Surface partial-load failures on the dashboard:

1. Component Design & UI State: Implement Surface partial-load failures on the dashboard with clean component decoupling, responsive layouts, accessible forms/modals, and robust loading/skeleton/error boundaries.
2. Web3 & Client Logic: Wire real-time state streams, optimistic UI updates, and seamless Freighter wallet transaction signatures with user-friendly error alerts for rejections/timeouts.
3. Comprehensive Test Suite: Add component and unit tests (Vitest / Jest + React Testing Library) verifying state changes, input sanitization, and edge-case rendering.
4. Production Verification: Confirm zero TypeScript errors (noImplicitAny), zero ESLint/Prettier warnings, and clean production build (pnpm build).

💡 Why Assigning Me Directly Benefits You:

• Zero Maintenance Burden: Pixel-perfect UI with strict typing and responsive states that work out of the box.
• Rapid Turnaround: Ready to deliver a production-ready PR within 12–24 hours, clearing this task quickly.
• Track Record: 28 merged Web3 PRs — zero review ping-pong and immediate alignment with your conventions.

[ZacLou]

Closing — the failedCount is already computed and displayed via the partialError banner in app/dashboard/page.tsx (lines 166-168, 306-318). The banner shows the count and a Retry button. No additional work needed.

[shobhamerabacha-star]

Hi everyone,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Build Surface partial-load failures on the dashboard with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!