-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Enable Lint Rule: line-length-limit #5540
Conversation
Signed-off-by: Vamshi Maskuri <[email protected]>
@yurishkuro I have used the
It has fixed most of it but still emits the lint errors for comments. Can comments also need fixes or add ignore? |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5540 +/- ##
==========================================
- Coverage 96.20% 96.18% -0.02%
==========================================
Files 327 327
Lines 16007 18719 +2712
==========================================
+ Hits 15399 18005 +2606
- Misses 432 538 +106
Partials 176 176
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Sorry, but I am not going to review 519 files. There was a clear comment in the config that the default length is not acceptable to us. |
Yes, the config contains 80 is too small :) Okay, will divide it into multiple PRS. What could be an acceptable line length limit? I am thinking of 120 which I have seen in a Google article on the recommended line length limit for Golang or any suggestions? |
How many breaks would be detected with 120? |
Signed-off-by: Vamshi Maskuri <[email protected]>
Ok, I have made changes and here are about 80 and 120 lll changes will reflect in the codebase: 80 lll - 18k+ lines and 519 files changed @yurishkuro Maybe we can go with 120. WDYT? |
213 files is still too many, not worth the effort. |
@yurishkuro For 150 there are 81 files changed |
still not worth it. I don't want to spend an hour reviewing such changes that provide little benefit. I usually try to fix long lines when making changes in the code, as a side effect. |
ok! Closing |
Which problem is this PR solving?
Description of the changes
How was this change tested?
make lint
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test