fullstorydev / fullstorydev/grpcurl

Un-quoted integer response values

Open
#272 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
12.8k
Forks
580
Avg merge
1h 8m
Merged PRs (30d)
5

Description

When making a request to a gRPC method returning a message that contains an integer, the JSON structure printed to stdout wraps these numbers in double quoues.

E.g.:
```bash
> grpcurl localhost:50051 Service.Method
{
"value": "12"
}
```
The same also applies to repeated integers, in which case the output would be e.g. `{ "value": ["1", "2", "3"] }`, despite `value`, in this example, being a `repeated int64`.

Is there a reason for this behaviour? Is it possible to disable it, i.e. to tell grpcurl to format them as unqouted numbers?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files or tests. Start by tracing grpcurl's JSON output entry point and checking the protobuf JSON rules for integer fields, then determine how an opt-out could be exposed. Done means integer and repeated-integer values can be emitted without quotes when requested, while existing output remains unchanged by default.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, grpc
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.