Skip to content

Commit 7547e3d

Browse files
committed
Fix indexing typos
There were some inconsistencies about the indexing of the examples. In some places the txid starting with "91261eaf..." was indexed with a 1, but it was reported as the first element of the array returned by the command `bitcoin-cli listunspent` (an array with index starting from 0) and later, in the same chapter, the same txid was reported as the element with index 0 of the array returned by the same command. Searching in text the txid I deduced that the correct indexing for that txid was 1. So I made changes accordingly.
1 parent 36b946f commit 7547e3d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

04_2__Interlude_Using_JQ.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ $ bitcoin-cli sendrawtransaction $signedtx
5151

5252
Grabbing data out of a JSON object is easy, but what if that JSON object is in a JSON array? The `listunspent` command offers a great example, because it'll usually contain a number of different transactions. What if you want to capture specific information from _one_ of them?
5353

54-
When working with a JSON array, the first thing you need to do is tell JQ which index to access. For example, you might have looked through your transactions in `listunspent` and decided that you wanted to work with the second of them. You use `'.[1]'` to access that first element. The `[]` says that we're referencing a JSON array and the `0` says we want the 0th index.
54+
When working with a JSON array, the first thing you need to do is tell JQ which index to access. For example, you might have looked through your transactions in `listunspent` and decided that you wanted to work with the second of them. You use `'.[1]'` to access that second element. The `[]` says that we're referencing a JSON array and the `1` says we want the 1st index.
5555
```
5656
$ bitcoin-cli listunspent | jq -r '.[1]'
5757
{
@@ -68,7 +68,7 @@ $ bitcoin-cli listunspent | jq -r '.[1]'
6868
"safe": true
6969
}
7070
```
71-
You can then capture an individual value from that selected array by (1) using a pipe _within_ the JQ arguments; and then (2) requesting the specific value afterward, as in the previous example. The following would capture the `txid` from the 0th JSON object in the JSON array produced by `listunspent`:
71+
You can then capture an individual value from that selected array by (1) using a pipe _within_ the JQ arguments; and then (2) requesting the specific value afterward, as in the previous example. The following would capture the `txid` from the 1st JSON object in the JSON array produced by `listunspent`:
7272
```
7373
$ bitcoin-cli listunspent | jq -r '.[1] | .txid'
7474
91261eafae15ea53dedbea7c1db748c52bbc04a85859ffd0d839bda1421fda4c

0 commit comments

Comments
 (0)