-
Notifications
You must be signed in to change notification settings - Fork 16
json-parser: basic support for ShellCheck's JSON output #83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b73278e to
4e08114
Compare
|
I think this is safe to be merged. We can extend the support for ShellCheck's JSON output in subsequent merge requests. |
jamacku
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... which is produced by `shellcheck --format=json1 ...` Fixes: csutils#75 Closes: csutils#83
4e08114 to
5b7b712
Compare
|
@jamacku Good catch! Fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks great but I'd drop the Fixes: from the commit message. The issue was specifically asking about handling of ShellCheck's suggestions which are still marked as a TODO.
Edit: Maybe Related: is more appropriate.
... which is produced by `shellcheck --format=json1 ...` Related: csutils#75 Closes: csutils#83
5b7b712 to
3ab6fbf
Compare
|
@lzaoral You are right. Fixed. |
lzaoral
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @kdudka!
|
@lzaoral Note that using |
|
Sorry, @kdudka. I did not know that and it is a rather stupid behaviour. |
|
My bad. The issue was explicitly linked with the pull request on GitHub. The use of |
... which is produced by
shellcheck --format=json1 ...