-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
REPL inspection outputs in CLI for Continuous Integration #189
Comments
Currently, Evans doesn't support such feature... (I'm going to plan to implement it in the nearly future, but not now) Thanks. |
@ktr0731 thank you! Appreciated your reply... let me know when you guys do it! |
I don't have much time to develop Evans, so I can't say when I can do it... |
@ktr0731 Sounds good... I just need the same output of the CLI taking a proto, so it shouldn't be too far from what you already have... |
I will try working on it during |
@ktr0731 Here's the design I wanna use: Show Packages
Show Services
Describe Messages
|
Looks good 👍 In addition, I think that it is better to format output with JSON in almost cases because we can combine other tools such like Example JSON output: {
"packages": [
{
"package": "api"
}
]
} {
"services": [
{
"service": "Example",
"rpc": "Unary",
"request type": "SimpleRequest",
"response type": "SimpleResponse"
},
{
"service": "Example",
"rpc": "UnaryMessage",
"request type": "UnaryMessageRequest",
"response type": "SimpleResponse"
},
{
"service": "Example",
"rpc": "UnaryRepeated",
"request type": "UnaryRepeatedRequest",
"response type": "SimpleResponse"
},
... |
Happy 2020! |
This feature is now implemented in v0.9.0 🎉 |
Is it possible to use Evans to output the properties of a given Proto? I just want to use Evans to instrospect Protos for Rapid development and I'd like to show the output of Evans in a CI job... I need to show the following:
The flow of what I'm looking for is in the REPL, but an as CI is automated, I need to get the same outputs like the ones below...
thank you
The text was updated successfully, but these errors were encountered: