Repository navigation
Please add support for ShellCheck JSON format #75
Description
Activity
Hmm, have you tried
json1format,jsonseems to be marked as legacy.json1works as expected. My bad.- added a commit that references this issue
on Sep 8, 2022 I have submitted draft pull request #83 that implements the basic support of the JSON format produced by ShellCheck. We yet need to figure out how to represent the information in the
fixkey such that it works with all the output formats supported bycsdiff.- linked a pull request that will close this issuejson-parser: basic support for ShellCheck's JSON output #83
on Sep 8, 2022
ShellCheck can suggest a possible solution of the reported defect. Unfortunately, this data isn't available in
gccformat. It would be nice ifcsdiffcould parse ShellCheck JSON format, which contains possible fix underfixkey.Example:
{ "comments": [ { "file": "myotherscript", "line": 2, "endLine": 2, "column": 1, "endColumn": 2, "level": "error", "code": 1035, "message": "You need a space after the [ and before the ].", "fix": null }, { "file": "myscript", "line": 2, "endLine": 2, "column": 6, "endColumn": 8, "level": "warning", "code": 2039, "message": "In POSIX sh, echo flags are undefined.", "fix": null }, { "file": "myscript", "line": 2, "endLine": 2, "column": 9, "endColumn": 11, "level": "info", "code": 2086, "message": "Double quote to prevent globbing and word splitting.", "fix": { "replacements": [ { "line": 2, "endLine": 2, "precedence": 7, "insertionPoint": "afterEnd", "column": 9, "replacement": "\"", "endColumn": 9 }, { "line": 2, "endLine": 2, "precedence": 7, "insertionPoint": "beforeStart", "column": 11, "replacement": "\"", "endColumn": 11 } ] } } ] }Having this kind of information would be very useful for:
Thanks for working on this project! 👍