Skip to content
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

Please make a new release! #963

Closed
moorara opened this issue Jun 28, 2019 · 6 comments
Closed

Please make a new release! #963

moorara opened this issue Jun 28, 2019 · 6 comments

Comments

@moorara
Copy link

moorara commented Jun 28, 2019

When generating our source codes using protoc, we always install the latest version of grpc-gateway since protoc does not work in Go modules mode.

When importing generated codes in our repos, we use Go modules and we use the latest release of grpc-gateway.

Problem:

Currently, grpc-gateway has a breaking change on master branch which is not yet released. So, we cannot fix it our repos unless we import the grpc-gateway module from master instead of semantically versioned releases.

@johanbrandhorst
Copy link
Collaborator

What error are you seeing? I was under the impression the last error was fixed with the latest release.

@johanbrandhorst
Copy link
Collaborator

Also, there's no reason protoc shouldn't work in go modules mode that I know of, this repo uses modules and protoc successfully. I would recommend that you version the generator together with your runtime dependency. With Go modules that is done via tool dependencies: https://github.com/golang/go/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module

@moorara
Copy link
Author

moorara commented Jun 28, 2019

@johanbrandhorst The runtime.NewPattern accepts one more argument which is runtime.AssumeColonVerbOpt(true)

@johanbrandhorst
Copy link
Collaborator

This is included in the 1.9.2 release: https://github.com/grpc-ecosystem/grpc-gateway/blob/v1.9.2/runtime/pattern.go. 1.9.2 should work with master (though you should ideally still not use master and a release at the same time). Are you seeing this problem on 1.9.2?

@moorara
Copy link
Author

moorara commented Jun 28, 2019

@johanbrandhorst You're right. 1.9.2 includes that change. For some reason, when I run go mod does not pick up the 1.9.2 and it picks up 1.9.0 release for our projects.

@moorara moorara closed this as completed Jun 28, 2019
@johanbrandhorst
Copy link
Collaborator

I've just released 1.9.3, FYI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants