Open ainar-g opened 5 years ago
While we're at it, we could probably also mark cases where people use `raw strings`
instead of "usual strings"
in imports.
I feel like this would be a really good candidate for an autofix tool, but there aren't any of those in go-tools yet, I think?
@fortytw2 gofmt
and goimports
kind of do that. They sort imports alphabetically and put stdlib imports into a group of their own, but they don't further divide external imports into hostname groups.
It's not uncommon to see imports like this in a project:
Which should really be
In fact, even the official Style Guide says so. I think that this is stylecheck-worthy.