What problem does your feature solve?
Plugins may want to take advantage of the transaction pipeline but today it is coupled the config::Args. Plugins have to import the entire cli in order in order to call tx::sim_sign_and_send_tx and have no way to use the transaction pipeline more flexibly, like to execute only a subset of the steps.
What would you like to see?
a stellar-tx-pipeline crate that is a minimal version of the transaction pipeline that can be used behind a Sign trait, with the keystore as a separate optional dependency.
What alternatives are there?
Reimplement parts of the transaction pipeline in every plugin or import the entire CLI.
What problem does your feature solve?
Plugins may want to take advantage of the transaction pipeline but today it is coupled the
config::Args. Plugins have to import the entire cli in order in order to calltx::sim_sign_and_send_txand have no way to use the transaction pipeline more flexibly, like to execute only a subset of the steps.What would you like to see?
a
stellar-tx-pipelinecrate that is a minimal version of the transaction pipeline that can be used behind a Sign trait, with the keystore as a separate optional dependency.What alternatives are there?
Reimplement parts of the transaction pipeline in every plugin or import the entire CLI.