-
Notifications
You must be signed in to change notification settings - Fork 1
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
Move to OPAQUE
#811
Move to OPAQUE
#811
Conversation
The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).
|
@@ -43,7 +43,6 @@ install: ## Install all binaries | |||
.PHONY: lint | |||
lint: $(BIN)/golangci-lint $(BIN)/buf ## Lint Go and protobuf | |||
test -z "$$($(BIN)/buf format -d . | tee /dev/stderr)" | |||
$(GO) vet ./... |
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.
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.
think we can use golangci-lint
to run go vet
anyway, so good to consolidate.
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.
The proto generated code here is only used internally, right? Other consumers use gen SDK definitions?
It's used also in the BSR backend code, but directly from the BSR, when syncing these modules. I'll tag you in that PR. |
@@ -43,7 +43,6 @@ install: ## Install all binaries | |||
.PHONY: lint | |||
lint: $(BIN)/golangci-lint $(BIN)/buf ## Lint Go and protobuf | |||
test -z "$$($(BIN)/buf format -d . | tee /dev/stderr)" | |||
$(GO) vet ./... |
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.
think we can use golangci-lint
to run go vet
anyway, so good to consolidate.
Fixes #813