submitBatch: typed BatchPartiallySubmittedError

[Jaydbrown]

Callers currently must inspect outcomes[] to notice a mid-batch failure. Throw (or expose) a typed error carrying firstFailureIndex and the skipped indices.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[achebejohnpaul]

Am a full-Stack Engineer focused on frontend, backend, APIs, automation, and modern web technologies. Passionate about solving real-world problems, contributing to open source, and delivering clean, scalable, review-ready solutions.

[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 submitBatch: typed BatchPartiallySubmittedError:

1. Component Design & UI State: Implement submitBatch: typed BatchPartiallySubmittedError 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.

[Ranjeet2063]

Hi maintainers,

I have resolved this issue by adding the typed BatchPartiallySubmittedError and the throwOnPartial option to submitBatch in PR #686:
#686

Highlights:

• Added BatchPartiallySubmittedError with firstFailureIndex, skippedIndices, and outcomes in src/errors.ts
• Added throwOnPartial to BatchSubmitOptions in src/batch-tx.ts
• Added unit tests in src/tests/batch-submit.test.ts (all 21 tests green)
• Verified full build

[Fading-Dev]

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

I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.

I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.

Let me know if I can get started, and I'll provide updates as I progress.