docs: clarify operation-level source account override - #2867
perroBlanco0 wants to merge 1 commit into
Conversation
The transactions concept page mentioned an "operation override" for the source account without explaining what it meant or linking to where it's documented. Point readers to the existing note in the List of Operations section that already explains per-operation source accounts. Fixes stellar#1022
|
PR Preview: torn down |
| Transactions are atomic. Meaning if one operation in a transaction fails, all operations fail, and the entire transaction is not applied to the ledger. | ||
|
|
||
| Operations are executed for the source account of the transaction unless an operation override is defined. | ||
| Operations are executed for the source account of the transaction unless an operation specifies its own, different source account (see the note in the [List of Operations section](./list-of-operations.mdx)). |
There was a problem hiding this comment.
thanks for picking this up! i like how small this change is, and swapping out the undefined "operation override" term is the right fix.
the one thing i'd tweak: the linked note in List of Operations says basically the same thing this sentence now says (the parameter is optional, and it falls back to the transaction's source account). so a reader who clicks through doesn't learn anything new. the part #1022 is really worried about is what a different source account changes, mainly who has to sign. that can fit in about the same space:
| Operations are executed for the source account of the transaction unless an operation specifies its own, different source account (see the note in the [List of Operations section](./list-of-operations.mdx)). | |
| Each operation can specify its own source account; if it doesn't, it uses the transaction's source account. An operation's source account determines which account the operation acts on and whose signers must authorize it (see [Multisig](./signatures-multisig.mdx#multisig)). The transaction's source account always provides the sequence number, and it pays the fee unless the transaction is wrapped in a [fee-bump](#fee-bump-if-applicable). |
that keeps this a one-paragraph change with no new page, and it covers the signing concern without the full examples section the issue originally asked for.
The transactions concept page mentioned an "operation override" for the source account without explaining what it meant or linking to where it's documented. Point readers to the existing note in the List of Operations section that already explains per-operation source accounts.
Fixes #1022