As a developer, I'd like linted code to help with quality #65
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#65
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are around 40 warnings currently coming up on the code base from GoMetaLinter. These are things like:
num -= 1
withnum--
I'd like to clean up some of these warnings for the 2.0.0 release.
I'd also like to ensure that all files are formatted for the release.
Maybe there are other static analysis steps required?
I think this is a good idea. Is GoMetaLinter a vim package? Or provided with the go toolchain? I have generally been running
go fmt
on things, but that is about it. I definitely agree a consistent code style would be good to have by release time.EDIT: It seems that GoMetaLinter is deprecated in favor of golangci-lint.
Thanks for the heads up on GoMetaLinter being deprecated. vim-go changed the command
:GoMetaLinter
to use golangci-lint very recently, so it changed without my noticing...This, I think, gets closed by #83 but there may be more to do. Not sure. What do you think @asdf ?
Resolved by #83 , with some small documentation in #84. Thanks for the efforts, it looks really nice now.
Yay! No problem. Thanks for making the issue and shepherding me into doing things I know I should do, but often just choose laziness.