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
C:\cygwin64\home\mrt181\sourcecode\api-service\build\extracted-include-protos\main\google\protobuf\struct.proto: Input is shadowed in the --proto_path by "C:/cygwin64/tmp/polyglot-well-known-types1930180195804578592/google/protobuf/struct.proto". Either use the latter file as your input or reorder the --proto_path so that the former file's location comes first.
I can fix this by deleting this directory: C:\cygwin64\home\mrt181\sourcecode\api-service\build\extracted-include-protos\main\google
because polyglot includes it in the polyglot-well-known-types. But that directory is regenerated by my build jobs.
to only use my protos and the well-known ones but this gives me this error:
api/trading/v1/type/instrument.proto: File not found.
trading/v1/response/list_instruments_response.proto: Import "api/trading/v1/type/instrument.proto" was not found or had errors.
trading/v1/response/list_instruments_response.proto:11:14: "Instrument" is not defined.
list_instruments_response.proto has this import
import "api/trading/v1/type/instrument.proto";
How can I exclude the usage of the well-known-types?
I pull them in myself because I need those
The text was updated successfully, but these errors were encountered:
I updated today to 2.0.0 and since version 1.6.0 I get this error for this command
I can fix this by deleting this directory:
C:\cygwin64\home\mrt181\sourcecode\api-service\build\extracted-include-protos\main\google
because polyglot includes it in the polyglot-well-known-types. But that directory is regenerated by my build jobs.
So I tried to run this instead:
to only use my protos and the well-known ones but this gives me this error:
list_instruments_response.proto
has this importHow can I exclude the usage of the well-known-types?
I pull them in myself because I need those
The text was updated successfully, but these errors were encountered: