We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using desc is only useful on top level messages. Also support calling it for nested objects:
desc
myservice@localhost:50051> desc SayHelloRequest +---------------------+----------------------------+----------------+ | FIELD | TYPE | REPEATED | +---------------------+----------------------------+----------------+ | person | TYPE_MESSAGE | false | | | (Person) | | +---------------------+----------------------------+----------------+
Should be able to do something like desc Person, or desc com.HelloService.Person.
desc Person
desc com.HelloService.Person
The text was updated successfully, but these errors were encountered:
Currently, there are no ways to do it, but I think the behavior should be improved.
FYI: in the command-line mode, we can describe all messages such as:
$ evans -r cli desc api.Example: service Example { rpc SayHello ( .api.SayHelloRequest ) returns ( .api.SayHelloResponse ); } $ evans -r cli desc api.SayHelloRequest api.SayHelloRequest: message SayHelloRequest { Person person = 1; } $ evans -r cli desc api.Person api.Person: message Person { // something }
Sorry, something went wrong.
yeah it'd be real nice if we can do it in the repl, especialy with those long-nested message types. :)
No branches or pull requests
Using
desc
is only useful on top level messages. Also support calling it for nested objects:Should be able to do something like
desc Person
, ordesc com.HelloService.Person
.The text was updated successfully, but these errors were encountered: