SendFlowOutcome class sealed

What became of ONE send flow, addressed by flowId — the authoritative answer, published by SendController and consumed by whoever owns that flow's host report.

Why this exists instead of reading SendState. A report is a claim about ONE flow, and SendState is a GLOBAL rendering state with no flow identity on it — so a screen watching it can grade a payment that was never its own (two entries stacked on one controller). Worse, the controller legitimately DROPS a state write it must not perform: a landing that arrives after a session flip is swallowed by the instance-identity guard, and reading that silence as "nothing happened" claims no money moved over a transaction that was signed and broadcast. This channel carries the fact even when the state write is correctly refused.

The four angles of the review each reached one of those two shapes independently; they are the same defect, and this is the one mechanism that closes both.

Implementers

• SendFlowIndeterminate
• SendFlowNothingCreated
• SendFlowQueued
• SendFlowSent

Properties

flowId → int

The flow this is the terminal of. A consumer reports ONLY for the flow it owns — see SendController.flowId.

final

hashCode → int

The hash code for this object.

no setter, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited