python/jc
1
0
Fork 0
mirror of https://github.com/kellyjonbrazil/jc.git synced 2025-06-17 00:07:37 +02:00
Code Issues Releases Activity

fix -qq docs

Browse Source
This commit is contained in:
Kelly Brazil
2021-09-23 11:54:58 -07:00
parent 98a7686db4
commit dc1fd3ef1b
4 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -232,9 +232,9 @@ Most parsers load all of the data from STDIN, parse it, then output the entire J
#### Ignoring Errors #### Ignoring Errors
You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the `-q` cli option or the `quiet=True` argument with the `parse()` function. This will add a `_meta` object to the JSON output with a `success` attribute. If `success` is `true`, then there were no issues parsing the line. If `success` is `false`, then a parsing issue was found and `error` and `line` fields will be added to include a short error description and the contents of the unparsable line, respectively: You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the `-qq` cli option or the `ignore_exceptions=True` argument with the `parse()` function. This will add a `_meta` object to the JSON output with a `success` attribute. If `success` is `true`, then there were no issues parsing the line. If `success` is `false`, then a parsing issue was found and `error` and `line` fields will be added to include a short error description and the contents of the unparsable line, respectively:
Successfully parsed line with `-q` option: Successfully parsed line with `-qq` option:
```json ```json
{ {
"command_data": "data", "command_data": "data",
@ -243,7 +243,7 @@ Successfully parsed line with `-q` option:
} }
} }
``` ```
Unsuccessfully parsed line with `-q` option: Unsuccessfully parsed line with `-qq` option:
```json ```json
{ {
"_meta": { "_meta": {

6
man/jc.1
View File

@ -493,10 +493,10 @@ Note: Streaming parsers cannot be used with the "magic" syntax
\fBIgnoring Errors\fP \fBIgnoring Errors\fP
You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the \fB-q\fP cli option or the \fBquiet=True\fP argument with the \fBparse()\fP function. This will add a \fB_meta\fP object to the JSON output with a \fBsuccess\fP attribute. If \fBsuccess\fP is \fBtrue\fP, then there were no issues parsing the line. If \fBsuccess\fP is \fBfalse\fP, then a parsing issue was found and \fBerror\fP and \fBline\fP fields will be added to include a short error description and the contents of the unparsable line, respectively: You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the \fB-qq\fP cli option. This will add a \fB_meta\fP object to the JSON output with a \fBsuccess\fP attribute. If \fBsuccess\fP is \fBtrue\fP, then there were no issues parsing the line. If \fBsuccess\fP is \fBfalse\fP, then a parsing issue was found and \fBerror\fP and \fBline\fP fields will be added to include a short error description and the contents of the unparsable line, respectively:
.RS .RS
Successfully parsed line with \fB-q\fP option: Successfully parsed line with \fB-qq\fP option:
.RS .RS
{ {
@ -511,7 +511,7 @@ Successfully parsed line with \fB-q\fP option:
} }
.RE .RE
Unsuccessfully parsed line with \fB-q\fP option: Unsuccessfully parsed line with \fB-qq\fP option:
.RS .RS
{ {

6
templates/manpage_template
View File

@ -108,10 +108,10 @@ Note: Streaming parsers cannot be used with the "magic" syntax
\fBIgnoring Errors\fP \fBIgnoring Errors\fP
You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the \fB-q\fP cli option or the \fBquiet=True\fP argument with the \fBparse()\fP function. This will add a \fB_meta\fP object to the JSON output with a \fBsuccess\fP attribute. If \fBsuccess\fP is \fBtrue\fP, then there were no issues parsing the line. If \fBsuccess\fP is \fBfalse\fP, then a parsing issue was found and \fBerror\fP and \fBline\fP fields will be added to include a short error description and the contents of the unparsable line, respectively: You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the \fB-qq\fP cli option. This will add a \fB_meta\fP object to the JSON output with a \fBsuccess\fP attribute. If \fBsuccess\fP is \fBtrue\fP, then there were no issues parsing the line. If \fBsuccess\fP is \fBfalse\fP, then a parsing issue was found and \fBerror\fP and \fBline\fP fields will be added to include a short error description and the contents of the unparsable line, respectively:
.RS .RS
Successfully parsed line with \fB-q\fP option: Successfully parsed line with \fB-qq\fP option:
.RS .RS
{ {
@ -126,7 +126,7 @@ Successfully parsed line with \fB-q\fP option:
} }
.RE .RE
Unsuccessfully parsed line with \fB-q\fP option: Unsuccessfully parsed line with \fB-qq\fP option:
.RS .RS
{ {

6
templates/readme_template
View File

@ -155,9 +155,9 @@ Most parsers load all of the data from STDIN, parse it, then output the entire J
#### Ignoring Errors #### Ignoring Errors
You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the `-q` cli option or the `quiet=True` argument with the `parse()` function. This will add a `_meta` object to the JSON output with a `success` attribute. If `success` is `true`, then there were no issues parsing the line. If `success` is `false`, then a parsing issue was found and `error` and `line` fields will be added to include a short error description and the contents of the unparsable line, respectively: You may want to ignore parsing errors when using streaming parsers since these may be used in long-lived processing pipelines and errors can break the pipe. To ignore parsing errors, use the `-qq` cli option or the `ignore_exceptions=True` argument with the `parse()` function. This will add a `_meta` object to the JSON output with a `success` attribute. If `success` is `true`, then there were no issues parsing the line. If `success` is `false`, then a parsing issue was found and `error` and `line` fields will be added to include a short error description and the contents of the unparsable line, respectively:
Successfully parsed line with `-q` option: Successfully parsed line with `-qq` option:
```json ```json
{ {
"command_data": "data", "command_data": "data",
@ -166,7 +166,7 @@ Successfully parsed line with `-q` option:
} }
} }
``` ```
Unsuccessfully parsed line with `-q` option: Unsuccessfully parsed line with `-qq` option:
```json ```json
{ {
"_meta": { "_meta": {