fullstorydev / fullstorydev/grpcurl
[Feature] add flag to make the full output machine-readable, not only the message
- Dominant language
- Go
- Stars
- 12.8k
- Forks
- 580
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 5
Description
Currently only the message is formatted as json, when you set `--format json`.
desired output example:
```
grpcurl --print-output-machine-readable ...
# the output:
{
"response-headers": [
{"content-type": "application/grpc"}
],
"http-status-code": 200,
"response-message": {
"field1": 123
},
"response-message-bytes": "base64string=="
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing --format json handling and the code that assembles grpcurl's full output. Trace how response headers, HTTP status, response messages, and response bytes are currently produced. Done means the new flag emits the complete output in the structure shown while preserving existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100