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
{{ message }}
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
Prost substitutes protobuf well-known types, but because tower-grpc-build's Config::generate doesn't use prost's built-in Config::generate, those substitutions never occur. As a result, protobufs that use well-known types will fail to compile with tower-grpc-build, producing errors like this:
@seanmonstar I'm not sure. It seems that in #81 the substitution is kinda-sorta happening for a well-known type, which suggests that my assumption about substitutions not working is wrong.
Prost substitutes protobuf well-known types, but because tower-grpc-build's
Config::generate
doesn't use prost's built-inConfig::generate
, those substitutions never occur. As a result, protobufs that use well-known types will fail to compile with tower-grpc-build, producing errors like this:As a workaround, I'm replacing references to
super::super::google::protobuf::...
with their equivalents in our build.rs.The text was updated successfully, but these errors were encountered: