-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add "code" (shell) linter and format checker #32
Conversation
9f7e03f
to
9815e12
Compare
This uses: - shellcheck - shfmt behind the scenes
88e1a52
to
87132f8
Compare
Now that #1 is out this is rebased on top of the default branch. |
ed43508
to
878b92b
Compare
Branch is updated and rebased on top of the default branch. Lemme know what you want relaxed, commented, removed, etc. |
805b320
to
e416e5e
Compare
@@ -118,7 +118,7 @@ test_otp() { | |||
{ok, _} = application:ensure_all_started(crypto), io:format("crypto ok~n"), | |||
halt().' | |||
|
|||
if dyld_info ${OTP_DIR}/lib/crypto-*/priv/lib/crypto.so | tail -n +2 | grep -q openssl; then | |||
if dyld_info "${OTP_DIR}/lib/crypto-*/priv/lib/crypto.so" | tail -n +2 | grep -q openssl; then |
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.
That's handy!
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.
LGTM
As with the other one, I'm merging and it should be easy to revert if it causes issues in the default branch. |
@@ -0,0 +1,34 @@ | |||
--- | |||
"on": |
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.
"on"
I'm not a fan of this particular change but I get it and it's obviously not a deal breaker. Thank you for the PR!
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.
We can revert it. It's an option for the linter. I'll do it.
This uses:
behind the scenes.
After #1 is merged I don't mind either relaxing the rules or adapting the code. I've found, over use, that at least ShellCheck is very good at catching error-prone patterns and even helping make it more readable.
Closes #13.
Closes #14.