summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgithub-actions[bot] <github-actions[bot]@users.noreply.github.com>2023-07-23 08:39:27 +0000
committergithub-actions[bot] <github-actions[bot]@users.noreply.github.com>2023-07-23 08:39:27 +0000
commit4224920495a565facb295c7601a498c5ef53d008 (patch)
tree66f97bd187326f04a70e94bcfc7a8a37e9acf9c2
parentb490d459c320543e4f678ebcd352e3c50bc42318 (diff)
Update website
-rw-r--r--manual/index.html9
1 files changed, 9 insertions, 0 deletions
diff --git a/manual/index.html b/manual/index.html
index 632d8938..a2d65c95 100644
--- a/manual/index.html
+++ b/manual/index.html
@@ -204,6 +204,15 @@ using some command-line options:</p>
conjunction with filtering and the <code>reduce</code> and <code>foreach</code> syntax
to reduce large inputs incrementally.</p>
<ul>
+<li><code>--stream-errors</code>:</li>
+</ul>
+<p>Like <code>--stream</code>, but invalid JSON inputs yield array calues
+ where the first element is the error and the second is a path.
+ For example, <code>["a",n]</code> produces ["Invalid literal at line 1,
+ column 9",[1]]`.</p>
+<p>Implies <code>--stream</code>. Invalid JSON inputs produce no error values
+ when <code>--stream</code> without <code>--stream-errors</code>.</p>
+<ul>
<li><code>--slurp</code>/<code>-s</code>:</li>
</ul>
<p>Instead of running the filter for each JSON object in the