gofumpt VS pre-commit-golang

In the roadmap section[1] the author says it's more of an experiment with a possibility that some of the rules might end up in the original 'gofmt' tool. While I agree that Go having a de facto formatter built in is wonderful, there are some absolutely fantastic additions in 'gofumpt' that I do hope wind up in 'gofmt'

---

[1]: https://github.com/mvdan/gofumpt#roadmap

No. If you want more strict formatting, you can use https://github.com/mvdan/gofumpt. Apart from using that, there is literally no reason not to use it.

I am the author of go-global-update, the missing command to update globally installed go executables (like gofumpt, gopls, gotop, and other CLI tools you may have installed globally in your system - in your GOBIN directory).

I think that the one tool that might still be useful outside of gopls is goimports. It can be used as a gofmt replacement, that also automatically manages and removes imports. Gopls can integrate staticcheck and gofumpt, but my understanding is that they have to be installed manually. See the settings section for more on that(1).

I use gofumpt but I'm pretty sure it doesn't wrap either (and I don't want it to so we're good)

For those who may be interested, my go pre-commit hooks package has built-in support for gofumpt (along with a bunch if other linters):

https://github.com/TekWizely/pre-commit-golang

TekWizely / pre-commit-golang v1.0.0-rc.1

github / TekWizely / pre-ommit-golang

v1.0.0-beta.4 Support for staticcheck

v1.0.0-beta.2 Support for go mod tidy Support for goumpt

Quick Links: Project Page | Available Hooks | Installation | Releases

pre-commit-golang v1.0.0-beta.2