-
Notifications
You must be signed in to change notification settings - Fork 623
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
Reformatted the code #1572
Reformatted the code #1572
Conversation
Thanks but I think we should convert the entire script to a code style we agree on and then start requiring it, instead of spot pull requests. I'm about to start a discussion now. |
3f2c667
to
0c56cbc
Compare
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.
If we can determine the code style rules, this PR can become the one that will reformat the code |
I think it's better to wait for #1567 and then reformat the code on top of that, unless you want to force push all the time to handle conflicts. |
8b6a02a
to
a732d11
Compare
As mentioned in discussion #1573, I have reformatted the code according to the Google rules |
63f864a
to
de3cede
Compare
d362bcb
to
8c46cee
Compare
Fix a code style bug into the style stage
Fix a code style error into the shfmt command
Fix a code style bug
Add the scripts into the ciscripts/ directory to the lint and the style stages
Fix a code style bug
5e473f0
to
9a7b7df
Compare
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
Improve the code style of some pieces of code
d79cd53
to
dda4d99
Compare
The 80 character limited suggested in the Google style guide is actually too restrictive IMHO, makes too many statements, variable definitions, commands more difficult to read, and probably slower too in cases like this when you need to call the command many times. |
Kinda agree, however having too big lines its also not that good. Guess we can agree in being flexible with that rule, and apply the 80 Chars rule whenever possible but open some exceptions where it actually doesn't help much. |
For sure, one exception will be " not apply the limit if it make the code less readable and/or harder to parse mentally" |
@orazioedoardo could you approve and merge the request ? |
@giulio-coa I'm not sure I want to, as it is, considering this. To add, as I said before, this is much less readable than this. |
Ok then, let's try to not get lost here and not let this drag for too long. We should apply the 80 Line rule whenever it is possible, however let's not get too strict about it and be flexible when to use it or not. Let's get this merged when changes are applied, and later on if we feel that we should fix / review some lines, it can come on separate PR. |
Revert the code style of a piece of code
🎉 This PR is included in version 4.1.0-test.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
I did some style improvements