-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
feature/go-mod #107
feature/go-mod #107
Conversation
Keeping the vendor make the project retro compatible? If yes, I think we should keep saving the vendor. |
not sure starting from 1.13 go get uses google modules proxy by default, so I think we can drop vendoring and it would be safe https://golang.org/doc/go1.13 IMHO vendoring more fits to languages without normal packaging system, like C 20 years ago. modern Go doesn't need it :) |
Codecov Report
@@ Coverage Diff @@
## dev #107 +/- ##
=======================================
Coverage 98.31% 98.31%
=======================================
Files 8 8
Lines 473 473
=======================================
Hits 465 465
Misses 4 4
Partials 4 4 Continue to review full report at Codecov.
|
Very happy to see Go modules here :-) |
switch to go modules
Description
used this: https://blog.golang.org/migrating-to-go-modules
go mod vendor
https://github.com/golang/go/wiki/Modules#how-do-i-use-vendoring-with-modules-is-vendoring-going-away@johnfercher do we really vendoring?
Related Issue
resolve #101
Checklist