Update docs for isInBlock (rather late than never) (#1923)
* Update docs for isInBlock (rather late than never) * Only warn on isInBlock filtering
This commit is contained in:
@@ -18,8 +18,10 @@ const unsub = await api.tx.balances
|
||||
.signAndSend(alice, (result) => {
|
||||
console.log(`Current status is ${result.status}`);
|
||||
|
||||
if (result.status.isFinalized) {
|
||||
console.log(`Transaction included at blockHash ${result.status.asFinalized}`);
|
||||
if (result.status.isInBlock) {
|
||||
console.log(`Transaction included at blockHash ${result.status.asInBlock}`);
|
||||
} else if (result.status.isFinalized) {
|
||||
console.log(`Transaction finalized at blockHash ${result.status.asFinalized}`);
|
||||
unsub();
|
||||
}
|
||||
});
|
||||
@@ -27,7 +29,7 @@ const unsub = await api.tx.balances
|
||||
|
||||
As per all previous subscriptions, the transaction subscription returns in `unsub()` and the actual method has a subscription callback. The `result` object has 2 parts, `events` (to to covered in the next section) and the `status` enum.
|
||||
|
||||
When the `status` enum is in `Finalized` state (checked via `isFinalized`), the underlying value contains the block hash of the block where the transaction has been included. This does not mean the block is finalized, but rather applies to the transaction state, as no further updates will be received for this subscription.
|
||||
When the `status` enum is in `Finalized` state (checked via `isFinalized`), the underlying value contains the block hash of the block where the transaction has been finalized. `Finalized` will follow `InBlock`, which is the block where the transaction has been included. `InBlock` does not mean the block is finalized, but rather applies to the transaction state, where `Finalized` means that the transaction cannot be forked off the chain.
|
||||
|
||||
## Transaction events
|
||||
|
||||
|
||||
Reference in New Issue
Block a user