-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix import order #175
Milestone
Comments
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Imports at one point had a nice order to them - standard go packages first, external imports second, local imports third. Along the way of v1 release, in many places this got mixed up.
While we're paying attention to cleaning up for v1 release, we may as well re-establish it.
The text was updated successfully, but these errors were encountered: