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

Remove indirect github.com/golang/glog dependency of runtime package #1694

Merged
merged 3 commits into from
Sep 25, 2020

Conversation

jasonewang
Copy link
Contributor

@jasonewang jasonewang commented Sep 24, 2020

References to other Issues or PRs

Similar intended fix as #118

Have you read the Contributing Guidelines?

Yep

Brief description of what is fixed or changed

Remove glog in dependency of runtime package so projects that have forked glog can use grpc-gateway without a flag collision.

#1449 introduced the httprule import to mux.go which causes glog to be imported when runtime is imported.

Other comments

There are other glog imports in internal/, protoc-gen-grpc-gateway/, and protoc-gen-openapiv2/ that don't seem to cause flag collisions when creating a mux and using the generated .pb.gw.go files. I can remove or update those to use grpclog instead if desired.

@jasonewang jasonewang changed the title Remove glog in dependency of runtime package Remove indirect github.com/golang/glog dependency of runtime package Sep 24, 2020
@johanbrandhorst johanbrandhorst merged commit 52bae68 into grpc-ecosystem:v2 Sep 25, 2020
@johanbrandhorst
Copy link
Collaborator

Thanks for your contribution!

@johanbrandhorst
Copy link
Collaborator

Could you please cherry pick this against master?

@jasonewang
Copy link
Contributor Author

Could you please cherry pick this against master?

This dependency as far as I can tell doesn't exist in master because httprule/parse.go is only used in protoc-gen-grpc-gateway which isn't imported by any user code.

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

Successfully merging this pull request may close these issues.

3 participants