You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be a way to customize the behavior of goimports and gofmt so that the golang.org/x/... packages are grouped with the standard library.
I (and prob many others) consider them to be de-facto standard library packages. It's just annoying when goimports mixes it up with "regular" 3rd party packages.
The text was updated successfully, but these errors were encountered:
I think it's correct that category "golang.org/x" packages as 3rd party.
The "x" means "experimental" packages and might changed without any backward compatibility.
I understand that they don't have same backward compatibility promise.
I just want to configure goimports so for me (and other others) it gets grouped with standard library. That way, in the future (whether the API changes or not), when it gets moved to the standard library and the import path gets changed it looks nicer having to make a smaller change (i.e path change and/or removal) and not having to MOVE it to top + path change and/or removal.
There should be a way to customize the behavior of goimports and gofmt so that the
golang.org/x/...
packages are grouped with thestandard library
.I (and prob many others) consider them to be de-facto standard library packages. It's just annoying when goimports mixes it up with "regular" 3rd party packages.
The text was updated successfully, but these errors were encountered: