You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The grpc-gateway repo officially uses grpc_ecosystem_grpc_gateway as the Bazel workspace name, as demonstrated here.
In github.com/grpc-ecosystem/grpc-gateway, the same repo is referenced via a different name com_github_grpc_ecosystem_grpc_gateway.
This inconsistency causes build errors for me (and likely other people too).
Admittedly, the name prefixed with com_github (i.e., the name rules_proto chose) sounds more correct to me. But I don't think it is easy to convince grpc-gateway to change the workspace name just because of this.
What's an acceptable solution here?
The text was updated successfully, but these errors were encountered:
The grpc-gateway repo officially uses
grpc_ecosystem_grpc_gateway
as the Bazel workspace name, as demonstrated here.In
github.com/grpc-ecosystem/grpc-gateway
, the same repo is referenced via a different namecom_github_grpc_ecosystem_grpc_gateway
.This inconsistency causes build errors for me (and likely other people too).
Admittedly, the name prefixed with
com_github
(i.e., the name rules_proto chose) sounds more correct to me. But I don't think it is easy to convincegrpc-gateway
to change the workspace name just because of this.What's an acceptable solution here?
The text was updated successfully, but these errors were encountered: