-
Notifications
You must be signed in to change notification settings - Fork 117
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
Fix/naming conventions #156
Fix/naming conventions #156
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we ensure that the required naming conventions are verified during CI? Assuming that the naming violations were originally reported by staticcheck, it seems to me that this PR only changes the circle CI staticcheck execution to additionally remove SA1019.
Bellow is run from:
|
In the current state, with the deprecated stuff in, the only CI check to verify this until deprecated stuff is removed I can think of, is to save the current output and compare it each next run? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest the following changes so that the review of naming conventions is automated
- run
staticcheck --checks="all" ./...
in.circleci/config.yml
- add
//lint:file-ignore ST1003 to be removed in the next release
header to every*_deprecated*
file - ignore specific SA1019 errors with line annotations
//lint:ignore SA1019 to be removed in the next release
From my POV, the huge set of changes herein is approved after staticcheck --checks="all" ./...
pass
…ning full suite check
Great idea! Implemented. CI now runs checks with |
Closes #147.
Introducing new *API interfaces with the proper name of types, methods, and arguments.
Original API kept, but it have been deprecated. It will be removed in the next release
Files with completely deprecated API were put to *_deprecated.go files.
Some tests have been duplicated to test both new and original API. Tests testing deprecated API are placed in *deprecated_test.go files.
CHANGELOG.md updated
Rebased/mergeable
Tests pass