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

DEVPROD-7742 Fix current testifylint lint issues (autofix flag) #8603

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ZackarySantana
Copy link
Contributor

DEVPROD-7742

Description

Before merging in the fix for our linter and adding stricter rules, I'm doing smaller PRs to fix the current mistakes that our linter should be catching.

This PR fixes the testifylint lint issues through their autofix flag. I'll be putting up a separate flag to enable the linter and the manual fixes that couldn't be solved via their autofix flag.

For reference, this is their autofix chart(and more info in this readme).

Testing
Running golangci-lint run in my terminal results in no more lint errors. This pulls from the .golangci.yml file's configuration (which our linter task should be doing.

@ZackarySantana ZackarySantana requested a review from a team January 8, 2025 20:47
@ZackarySantana ZackarySantana self-assigned this Jan 8, 2025
@ZackarySantana
Copy link
Contributor Author

There are two extra commits, one is removing an unused package in a file after the autofix. The other is some malformed autofixes it applied (using positive rather than NotEmpty)

Copy link
Contributor

@Kimchelly Kimchelly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having this as a linter will save me from having to nitpick for these in CR again (especially the wrong argument order passed to assert.Equal)! Such a great improvement 🙏

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

Successfully merging this pull request may close these issues.

2 participants