-
Notifications
You must be signed in to change notification settings - Fork 819
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding goimports back into the build shell.
- Loading branch information
1 parent
2d8c351
commit 5ee93f8
Showing
1 changed file
with
2 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5ee93f8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean we can use packages that are not in the vendor tree?
5ee93f8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@slartibaartfast sorry, I'm not sure I understand the question?
5ee93f8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to be vague. Does the use of goimports mean that packages referenced in the import section of a go file will be imported and incorporated into the build if they are not found locally? And if so, does that mean that I could do something like submit a pr that imports a package such as github.com/gin-gonic/gin without breaking the build?
5ee93f8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got you. No, this is just adding the binary for goimports, so it's available in the Docker developer shell. That's it.