Golangci lint fixes #16
Merged
Conversation
This file contains hidden or 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
- Resolved linting issues across many files using automated fixes from golangci. - Adjustments include formatting, static analysis improvements, and adherence to linter rules. - Changes are non-functional and focus solely on improving code quality and consistency. This commit addresses widespread linter warnings/errors to ensure cleaner, more maintainable code.
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.
This PR fix lint issues in multiple files using golangci
Manual fixes
- Pass context around from main to downstream functions
- Parallelize all the tests
Auto fixes
- Resolved linting issues across many files using automated fixes from golangci.
- Adjustments include formatting, static analysis improvements, and adherence to linter rules.