[108] ISSUE-081: Add Soroban Transaction Preflight Example - #148
Merged
Dantama022 merged 2 commits intoJul 29, 2026
Conversation
|
@esthertitilayo-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
src/examples/81-transaction-preflight.ts, demonstrating the full Soroban preflight workflow: connect to RPC, fund an ephemeral fee-payer, build an invocation, run preflight simulation, extract the ledger footprint/authorization entries/resource fee, assemble the final transaction, then sign, submit, and poll for confirmation.68-soroban-contract-simulation(which stops after assembly), this example completes the lifecycle and explicitly explains how a full preflight differs from an ordinary read-only simulation.describePreflightFailurehelper that never throws and always returns actionable guidance.src/runner/catalog.tsand documents it inREADME.md(roadmap entry + Direct Run section).tests/transaction-preflight.test.tscovering footprint extraction (against a real constructedxdr.SorobanTransactionData), auth summarization, resource fee formatting, failure guidance, the preflight-vs-simulation explanation, runner registration, and README docs.validation.config.jsonexclusion entry for the new example (requires live Soroban RPC + deployed contract).src/validation/validation.config.json(a missing},/{between the67-soroban-contract-eventsand50-asset-issuer-discoveryexclusion entries) that was breakingtests/ledger-effects.test.tsand the full test suite.Test plan
npx eslint "src/**/*.ts" "tests/**/*.ts"clean on all changed/added filesnpx tsc --noEmit— no new errors introduced (pre-existing unrelated errors in72/73/75example files remain, untouched by this PR)npx jest tests/transaction-preflight.test.ts tests/ledger-effects.test.ts tests/runner.test.ts— all passingnpm test— full suite green (22 suites, 261 tests)Closes #108