Skip to content
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

Enforce line-length limits in linter #2484

Closed
rigelrozanski opened this issue Oct 12, 2018 · 4 comments
Closed

Enforce line-length limits in linter #2484

rigelrozanski opened this issue Oct 12, 2018 · 4 comments
Labels

Comments

@rigelrozanski
Copy link
Contributor

We should enforce the length of lines of code in the linter as to make it less arbitrary

#2236 (comment)

@alessio alessio added tooling dev tooling within the sdk and removed tooling dev tooling within the sdk labels Oct 21, 2018
alessio pushed a commit that referenced this issue Oct 21, 2018
@alessio alessio self-assigned this Oct 22, 2018
alessio pushed a commit that referenced this issue Oct 22, 2018
alessio pushed a commit that referenced this issue Oct 23, 2018
Closes: #2484

Install lll through get_tools.sh

Remove check_dev_tools target from Makefile

Shorten lines

Run make format

Set maximum line length to 120
alessio pushed a commit that referenced this issue Oct 23, 2018
Closes: #2484

Install lll through get_tools.sh

Remove check_dev_tools target from Makefile

Shorten lines

Run make format

Set maximum line length to 120
alessio pushed a commit that referenced this issue Oct 25, 2018
Closes: #2484

Install lll through get_tools.sh

Remove check_dev_tools target from Makefile

Shorten lines

Run make format

Set maximum line length to 120
@cwgoes
Copy link
Contributor

cwgoes commented Nov 4, 2018

Decided in favor of an optional linter step - #2546 (comment).

@alessio alessio removed their assignment Nov 30, 2018
@alessio
Copy link
Contributor

alessio commented Nov 30, 2018

Deassigning myself. I'm presently not doing work on this.

@rigelrozanski
Copy link
Contributor Author

Having started reflecting on line lengths and code aesthetics intensely over the past while. I no longer believe the optimal solution actually contains "one size fits all" maximum line length. For instance I think that in specific situations, code can actually be much clearer when it is more compact and thus should allow for greater than 100 character lines. One key example of this is struct definition, where we provide a comment for each field on the line of the field and allow it to. I think what's important in this situation is there there is very little logic on each of these lines, Thus I could see it appropriate that these line lengths actually extend to 140 character. I think a better "max size" might be for the maximum amount of logic per line not the maximum character length.

Anyways, I no-longer think this issue's proposal is a good idea, I've started parsing out the thesis of what I know to be the optimal code aesthetic linting ruleset here: https://github.com/rigelrozanski/aes-fmt (still very much a WIP and developing ideas)

@cwgoes
Copy link
Contributor

cwgoes commented Nov 30, 2018

OK, I don't have a strong preference either, closing for now then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants