doc: markup jq as program role

Co-authored-by: Roberto Abdelkader Martínez Pérez <robertomartinezp@gmail.com>
This commit is contained in:
pancho horrillo
2019-12-11 11:38:29 +01:00
parent 4d2f0af941
commit 45de867b2d
2 changed files with 6 additions and 6 deletions
+1 -1
View File
@@ -123,7 +123,7 @@ You can list the active routes in the *Kapow!* server.
$ kapow route list
[{"id":"20c98328-0b82-11ea-90a8-784f434dfbe2","method":"GET","url_pattern":"/echo/{message}","entrypoint":"/bin/sh -c","command":"kapow get /request/matches/message | kapow set /response/body"}]
Or, if you want human-readable output, you can use ``jq``:
Or, if you want human-readable output, you can use :program:`jq`:
.. code-block:: console
:linenos:
+5 -5
View File
@@ -73,19 +73,19 @@ Sharing the Stats
**Junior**
``jq``? What is that command?
:program:`jq`? What is that command?
**Senior**
``jq`` is a wonderful tool for working with ``JSON`` data from the command
line. With ``jq`` you can extract data from a ``JSON`` document and it also
:program:`jq` is a wonderful tool for working with ``JSON`` data from the command
line. With :program:`jq` you can extract data from a ``JSON`` document and it also
allows you to generate a well-formed ``JSON`` document.
**Junior**
Let's use it, then!
How can we generate a ``JSON`` document with ``jq``?
How can we generate a ``JSON`` document with :program:`jq`?
**Senior**
@@ -105,7 +105,7 @@ Sharing the Stats
**Senior**
Bear with me, it gets better. You can add variables to the ``JSON`` and
``jq`` will escape them for you.
:program:`jq` will escape them for you.
.. code-block:: console