Fix golangci-lint "goconst" errors (WORKAROUND) #179
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
atc0005
force-pushed
the
i176-fix-goconst-linting-errors
branch
2 times, most recently
from
76c3ba0 to
54f9be9
Compare
- Create minimum (or near about) constants to resolve golangci-lint's goconst linting tests - Drop a good many TODO markers for further refactoring work This is meant to get the CI builds passing again and clearly note places that need further refinement for near-future focus work. refs #176
atc0005
force-pushed
the
i176-fix-goconst-linting-errors
branch
from
54f9be9 to
ed0662d
Compare
atc0005
changed the title
atc0005
changed the title
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.
Create minimum (or near about) constants to resolve golangci-lint's goconst linting tests
Drop a good many
TODOmarkers for further refactoring workThis is meant to get the CI builds passing again and clearly note places that need further refinement for near-future focus work.
fixes #176