-
Notifications
You must be signed in to change notification settings - Fork 513
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 nolintlint
linter and fix violations
#3650
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
spencerschrock
requested review from
justaugustus and
raghavkaul
and removed request for
a team
November 7, 2023 23:42
spencerschrock
temporarily deployed
to
integration-test
November 7, 2023 23:43 — with
GitHub Actions
Inactive
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3650 +/- ##
==========================================
- Coverage 76.12% 70.51% -5.62%
==========================================
Files 205 205
Lines 14051 14050 -1
==========================================
- Hits 10697 9907 -790
- Misses 2723 3568 +845
+ Partials 631 575 -56 |
raghavkaul
approved these changes
Nov 15, 2023
spencerschrock
force-pushed
the
lint/nolintlint
branch
from
November 15, 2023 19:22
bda2a87
to
86f3836
Compare
spencerschrock
temporarily deployed
to
gitlab
November 15, 2023 19:22 — with
GitHub Actions
Inactive
spencerschrock
temporarily deployed
to
integration-test
November 15, 2023 19:22 — with
GitHub Actions
Inactive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
linter change
What is the current behavior?
//nolint
directives aren't formatted properly and end up in doc strings. This syntax is from the docs here https://go.dev/doc/comment//nolint
directives are too broad and are hiding bugs.What is the new behavior (if this is a feature change)?**
The
nolintlint
linter is enabled to enforce directive comments//nolint
directives without a sublinter are prohibited. They should all include specific linter(s) so we don't hide other bugs. e.g.//nolint:my-linter,some-other-linter
.//nolint
directives are removedtwo loop aliasing bugs are fixed
Tests for the changes have been added (for bug fixes/features)
Which issue(s) this PR fixes
Fixes #3588
Special notes for your reviewer
This PR is large sorry. Here are the functional changes I've highlighted from the diff using some
grep
ing and trimminggit diff main | grep -E "^[+-]\s" | grep -v "nolint"`
simple alternative
simple alternative
simple alternative
This one is a loop alias bug you can view here.
Unused struct
moved dynamic error to a package level var:
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)