-
Notifications
You must be signed in to change notification settings - Fork 513
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
Whether I can get the structure of the request parameters and response parameters of the grpc interface, this is very useful to me #425
Comments
@l54808821, the This file includes the definitions from the proto source file that defines the elements you are listing or describing as well as all of the files it imports. Other Protobuf runtime APIs that support reflection often have a way to work with these descriptors. In Go, for example, it's various packages under |
@jhump Hello, "fullstorydev/grpcui" project this interface (" http://127.0.0.1:63806/metadata? method=team.Team.add ") return information is what I want, I wonder if it can be obtained by command in this project |
No, not quite. Most of the logic in this package uses the Go protobuf runtime's reflection facilities: https://pkg.go.dev/google.golang.org/protobuf/reflect As such, nearly everything works with descriptors (per my earlier reply). Only the browser JS code (which doesn't use a protobuf runtime so doesn't have any way to work with descriptors) uses this representation, for building the HTML form. As such this format is not available outside of the endpoint you highlighted. What exactly are you trying to do that would make this representation useful? |
@jhump I made a web tool that needed to get a preset request body based on the grpc interface, so |
Whether I can get the structure of the request parameters and response parameters of the grpc interface, this is very useful to me
The text was updated successfully, but these errors were encountered: