-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Service reflection can not handle directory paths with imported proto files #7146
Comments
Hi @nkoson -- sorry for the delayed response. But I would like to get more clarity here
I would like to understand the directory structure here more clearly. Could you maybe provide us with an example on how to reproduce this? |
This issue is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed. |
What version of gRPC are you using?
1.63.2
What version of Go are you using (
go version
)?1.21.0
What operating system (Linux, Windows, …) and version?
macOS 13.2
What did you do?
My proto file
api/proto/services/foo/v1/foo.proto
imports a file from another directory:
import "api/proto/v1/bar.proto";
and I instruct protoc with
-I ./
start the gRPC server and describe its services with
grpcurl
:(for the record, the issue persists in Postman as well)
However, if I change the import in
api/proto/services/foo/v1/foo.proto
toimport "bar.proto";
and instruct protoc with
-I ./api/proto/v1
then service reflection works fine.
What did you expect to see?
Service reflection should be able to traverse directories.
What did you see instead?
Service reflection only working when the import statement does not describe a directory path.
The text was updated successfully, but these errors were encountered: