-
Notifications
You must be signed in to change notification settings - Fork 339
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
chore: update go up to 1.14.2 #718
Changes from all commits
32028f6
7bcd8b0
2494c57
b49d8e6
1978638
fc477be
66dbc69
d59f6c1
7541c9e
ed77c1e
adcd384
1e62d08
6e6b350
5c717bb
d000975
64bb207
85b15af
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -45,10 +45,10 @@ dev/install/protobuf-wellknown-types:: ## Bootstrap: Install Protobuf well-known | |
&& echo "Protobuf well-known types $(PROTOC_VERSION) have been installed at $(PROTOBUF_WKT_DIR)" ; fi | ||
|
||
dev/install/protoc-gen-go: ## Bootstrap: Install Protoc Go Plugin (protobuf Go generator) | ||
go get -u github.com/golang/protobuf/protoc-gen-go@$(GOLANG_PROTOBUF_VERSION) | ||
go get github.com/golang/protobuf/protoc-gen-go@$(GOLANG_PROTOBUF_VERSION) | ||
|
||
dev/install/protoc-gen-validate: ## Bootstrap: Install Protoc Gen Validate Plugin (protobuf validation code generator) | ||
go get -u github.com/envoyproxy/protoc-gen-validate@$(PROTOC_PGV_VERSION) | ||
go get github.com/envoyproxy/protoc-gen-validate@$(PROTOC_PGV_VERSION) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why removing the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. At first, we install Maybe all dependencies should be installed without There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see. Well removing There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 to removing |
||
|
||
dev/install/ginkgo: ## Bootstrap: Install Ginkgo (BDD testing framework) | ||
# see https://github.com/onsi/ginkgo#set-me-up | ||
|
@@ -131,4 +131,4 @@ dev/install/golangci-lint: ## Bootstrap: Install golangci-lint | |
curl -sfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh| sh -s -- -b $(GOLANGCI_LINT_DIR) $(GOLANGCI_LINT_VERSION) | ||
|
||
dev/install/goimports: ## Bootstrap: Install goimports | ||
go get -u golang.org/x/tools/cmd/goimports | ||
go get golang.org/x/tools/cmd/goimports |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Hmm can we have a common target that gets arguments for PKG and COVERAGE to test and input the results to?
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.
Are you talking about something like this:
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.
Yes! At least we get a more structured testing pattern to follow. @jakubdyszkiewicz what do you think?
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.
Sure, as long as we've got a single
make test
target that tests everything (which I see we do) I'm ok with it