-
Notifications
You must be signed in to change notification settings - Fork 7
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
feature request: incorporate shellcheck for linting command blocks #191
Comments
Very selfishly interested in this. I might be able to take a stab at it if this is still desired. Would I be correct in thinking this would be more appropriate for sprocket now? |
We would certainly welcome that contribution! I've wanted this feature for a long time, but it hasn't made it up high enough in my priority list. I think this code should live in the |
Yeah I'd say this should live in |
Sure, would be happy to discuss! Looks like the linked Zulip channel is invite only, though. |
Oh, thanks for pointing that out! I've updated the link with the invitation code—could you try again? |
Co-authored-by: Clay McLeod <3411613+claymcleod@users.noreply.github.com>
Co-authored-by: Clay McLeod <3411613+claymcleod@users.noreply.github.com>
Co-authored-by: Clay McLeod <3411613+claymcleod@users.noreply.github.com>
This feature will be a complete rip-off from miniwdl. It's my favorite feature of
miniwdl check
and I want us to copy it.For completeness: link to
shellcheck
siteIt's been a while since I looked into this, but when I last looked there wasn't a good Rust crate for doing Bash linting.
miniwdl
shells out toshellcheck
and parses the resulting STDOUT for a nice user interface. We are probably going to be stuck doing the same, which isn't ideal bc it's not very robust. But linting command blocks is a great feature I really want us to have, and it's worth getting our hands a little dirty IMO.The text was updated successfully, but these errors were encountered: