You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat!: align Python API with TypeScript naming conventions
BREAKING CHANGE: Multiple API field and type renames to align with algokit-utils-ts
## Changes
### MultisigSubsignature
- Renamed \`address: str\` to \`public_key: bytes\` to match TypeScript's \`publicKey: Uint8Array\`
- Aligns with go-algorand canonical definition (\`Key PublicKey\` with wire key \`pk\`)
- Wire format unchanged - backward compatible at protocol level
### AppCallTransactionFields
- Renamed \`access\` to \`access_references\` to match TypeScript's \`accessReferences\`
- Wire key remains \`al\`
### Transaction
- Renamed \`app_call\` to \`application_call\` to match TypeScript's \`applicationCall\`
### SendAtomicTransactionComposerResults
- Removed backwards compatibility alias completely
- Use \`SendTransactionComposerResults\` instead"
Copy file name to clipboardExpand all lines: docs/markdown/capabilities/transaction.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Transaction management is one of the core capabilities provided by AlgoKit Utils
4
4
5
5
## Transaction Results
6
6
7
-
All AlgoKit Utils functions that send transactions return either a `SendSingleTransactionResult` or `SendAtomicTransactionComposerResults`, providing consistent mechanisms to interpret transaction outcomes.
7
+
All AlgoKit Utils functions that send transactions return either a `SendSingleTransactionResult` or `SendTransactionComposerResults`, providing consistent mechanisms to interpret transaction outcomes.
-`SendAppCreateTransactionResult` - Adds `app_id` and `app_address`
32
32
33
-
### SendAtomicTransactionComposerResults
33
+
### SendTransactionComposerResults
34
34
35
-
When using the atomic transaction composer directly via `TransactionComposer.send()` or `TransactionComposer.simulate()`, you’ll receive a `SendAtomicTransactionComposerResults`:
35
+
When using the atomic transaction composer directly via `TransactionComposer.send()` or `TransactionComposer.simulate()`, you’ll receive a `SendTransactionComposerResults`:
36
36
37
37
```python
38
38
@dataclass
39
-
classSendAtomicTransactionComposerResults:
39
+
classSendTransactionComposerResults:
40
40
group_id: str# The group ID if this was a transaction group
41
41
confirmations: list[AlgodResponseType] # The confirmation info for each transaction
42
42
tx_ids: list[str] # The transaction IDs that were sent
@@ -64,8 +64,8 @@ These types extend the base transaction results to add an `abi_value` field that
64
64
Different interfaces return different result types:
Copy file name to clipboardExpand all lines: docs/source/capabilities/transaction.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Transaction management is one of the core capabilities provided by AlgoKit Utils
4
4
5
5
## Transaction Results
6
6
7
-
All AlgoKit Utils functions that send transactions return either a `SendSingleTransactionResult` or `SendAtomicTransactionComposerResults`, providing consistent mechanisms to interpret transaction outcomes.
7
+
All AlgoKit Utils functions that send transactions return either a `SendSingleTransactionResult` or `SendTransactionComposerResults`, providing consistent mechanisms to interpret transaction outcomes.
-`SendAppCreateTransactionResult` - Adds `app_id` and `app_address`
32
32
33
-
### SendAtomicTransactionComposerResults
33
+
### SendTransactionComposerResults
34
34
35
-
When using the atomic transaction composer directly via `TransactionComposer.send()` or `TransactionComposer.simulate()`, you'll receive a `SendAtomicTransactionComposerResults`:
35
+
When using the atomic transaction composer directly via `TransactionComposer.send()` or `TransactionComposer.simulate()`, you'll receive a `SendTransactionComposerResults`:
36
36
37
37
```python
38
38
@dataclass
39
-
classSendAtomicTransactionComposerResults:
39
+
classSendTransactionComposerResults:
40
40
group_id: str# The group ID if this was a transaction group
41
41
confirmations: list[AlgodResponseType] # The confirmation info for each transaction
42
42
tx_ids: list[str] # The transaction IDs that were sent
@@ -65,8 +65,8 @@ Different interfaces return different result types:
0 commit comments