Struct TransactionState 

pub struct TransactionState {
    pub transaction: Transaction,
    pub splits: Vec<Split>,
    pub transaction_tags: Vec<Tag>,
    pub split_tags: Vec<(Uuid, Tag)>,
    pub prices: Vec<Price>,
    pub account_names: HashMap<Uuid, String>,
}

Fields

transaction: Transaction

splits: Vec<Split>

transaction_tags: Vec<Tag>

split_tags: Vec<(Uuid, Tag)>

prices: Vec<Price>

account_names: HashMap<Uuid, String>

Display name per posting account id, so the serializer can expose SPLIT-ACCOUNT-NAME to trigger scripts without an in-script account lookup. Empty for an account whose name is unknown at build time.

Implementations

impl TransactionState

pub fn new(transaction: Transaction) -> Self

pub fn with_account_names(self, names: HashMap<Uuid, String>) -> Self

pub fn with(self, entities: Vec<FinanceEntity>) -> Self

pub fn with_split_tags(self, tags: Vec<(Uuid, Tag)>) -> Self

pub fn with_note(self, note: Option<String>) -> Self

pub fn run_scripts( self, executor: &ScriptExecutor, scripts: &[(Uuid, Vec<u8>)], ) -> Result<ScriptRunReport, ServerError>

Runs each script against the current state, accumulating per-script failures into a structured ScriptRunReport rather than swallowing them silently. The state field reflects every script that successfully produced entities; failed scripts are recorded in failures and don’t abort the batch — subsequent scripts still observe state mutations from earlier successes.

The outer Result reserves ServerError for genuine orchestration failures (entity-apply errors), keeping script-side failures structurally separate. Callers that want the previous “first-failure-aborts” semantics can chain with ScriptRunReport::into_state_or_first_failure.