When we have nested message definitions, grpcurl is unable to resolve some symbols. I have found that by injecting a different package name it will resolve fine, so there may be an issue in how we calculate the package names of modules.
This PR demonstrates this in the example app.
regenerate the example protos ./generate_protos.sh
nested message does not resolve (when you comment out the package overwrite code in server.ex)
❯ grpcurl -plaintext 127.0.0.1:50051 describe example.helloworld.HelloSpec.Spec
Failed to resolve symbol "example.helloworld.HelloSpec.Spec": Symbol not found: example.helloworld.HelloSpec.Spec
When we have nested message definitions, grpcurl is unable to resolve some symbols. I have found that by injecting a different package name it will resolve fine, so there may be an issue in how we calculate the package names of modules.
This PR demonstrates this in the example app.
./generate_protos.sh
iex -S mix
This may be related to https://github.com/elixir-grpc/grpc-reflection/issues/20