python/jc
1
0
Fork 0
mirror of https://github.com/kellyjonbrazil/jc.git synced 2026-06-19 22:28:17 +02:00
Code Issues Releases Activity

change _meta to _jc_meta

Browse Source
This commit is contained in:
Kelly Brazil
2021-09-23 13:07:10 -07:00
parent abd20dfe36
commit e7ddcfb83f
5 changed files with 14 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
templates/manpage_template
+3 -3
View File
@@ -108,7 +108,7 @@ Note: Streaming parsers cannot be used with the "magic" syntax
\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-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:
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_jc_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
Successfully parsed line with \fB-qq\fP option:
@@ -117,7 +117,7 @@ Successfully parsed line with \fB-qq\fP option:
"command_data": "data",
"_meta": {
"_jc_meta": {
"success": true
@@ -130,7 +130,7 @@ Unsuccessfully parsed line with \fB-qq\fP option:
.RS
{
"_meta": {
"_jc_meta": {
"success": false,
templates/readme_template
+3 -3
View File
@@ -155,13 +155,13 @@ Most parsers load all of the data from STDIN, parse it, then output the entire J
#### 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 `-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:
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 `_jc_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 `-qq` option:
```json
{
"command_data": "data",
"_meta": {
"_jc_meta": {
"success": true
}
}
@@ -169,7 +169,7 @@ Successfully parsed line with `-qq` option:
Unsuccessfully parsed line with `-qq` option:
```json
{
"_meta": {
"_jc_meta": {
"success": false,
"error": "error message",
"line": "original line data"