Export resolveFee and document fee / feeMultiplier precedence

[Jaydbrown]

#509 added fee / feeMultiplier to ConduitConfig and resolveFee() in soroban.ts. Re-export resolveFee from the entry point and add a README section on precedence (explicit fee wins, else feeMultiplier * BASE_FEE, else BASE_FEE).

[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 Export resolveFee and document fee / feeMultiplier precedence:

1. Component Design & UI State: Implement Export resolveFee and document fee / feeMultiplier precedence 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 by re-exporting resolveFee from the SDK entry point and documenting the exact precedence hierarchy (fee -> feeMultiplier * BASE_FEE -> BASE_FEE) in README.md in PR #683:
#683

Highlights:

• Re-exported resolveFee in src/index.ts
• Added Fee Resolution & Precedence guide and cleaned up table rendering in README.md
• Added entry point export verification in src/tests/soroban-fee-config.test.ts (6/6 tests passing, 82/82 test files green)
• Verified clean production rollup bundle build (npm run build)

[Jafeth012]

I’d like to take on this task; I have strong experience building TypeScript SDKs and writing clear developer documentation, so I can seamlessly re-export resolveFee from the main index entry point, add comprehensive unit tests to verify the fee versus feeMultiplier fallbacks, and write a concise README section documenting the exact precedence logic (explicit fee > feeMultiplier * BASE_FEE > BASE_FEE) to complete PR #660 quickly—assign this to me and I will submit a PR today!