-
Notifications
You must be signed in to change notification settings - Fork 16
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
[COMPARISION] shellcheck-sarif/sarif-fmt
🆚 csgrep
#137
Comments
shellcheck-sarif/sarif/fmt
🆚 csgrep
shellcheck-sarif/sarif-fmt
🆚 csgrep
The rules generated by |
@lzaoral We already provide help text to be shown by GitHub:
Do we have any other information to put into |
Yes, I know. But according to the documentation above, everything from this list:
|
@kdudka Would it make sense to use JSON output instead of the the GCC format of ShellCheck in OSH? |
That could be difficult because we use |
Actually, we use |
Thanks to csutils/csmock#182, csmock and consequently OSH now use ShellCheck with the JSON output format only. |
This is not an actual issue in csdiff. I will demonstrate the differences between
sarif-rs
utilities (soon available in Fedora) andcsutils
.The main purpose of this issue is to show how other tools deal with the over-complicated specification of the SARIF format. And maybe get some inspiration for new features or enhancements.
Shell
shellcheck --format=json1 src/index.sh | csgrep --mode=sarif
generated SARIF
shellcheck --format=json shell.sh | shellcheck-sarif
generated SARIF
Rust
Support for clippy is currently missing in
csutils
, so this is only an example withsarif-rs
utils.cargo clippy --message-format=json | clippy-sarif
csgrep is able to parse SARIF format produced by
clippy-sarif
.The text was updated successfully, but these errors were encountered: