grpc-ecosystem/grpc-gateway

Inconsistent enum behaviour

Open

#354 创建于 2017年4月13日

在 GitHub 查看
 (1 评论) (2 反应) (0 负责人)Go (16,971 star) (2,250 fork)batch import
help wanted

描述

Given the following messages and enumeration:

message NameCheckResponse {
    Result result = 1;
}

message MultiNameCheckResponse {
    map<string, Result> results = 1;
}

enum Result {
    AVAILABLE = 0;
    UNAVAILABLE = 1;
    UNKOWN = 2;
}

The returned value in case of the first message is the name of the enum. In the second case, it's the numeric value.

Is this behaviour intended?

贡献者指南

技术栈
gogrpcrest api
领域
backendapi
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
protobuf basicsgRPC concepts
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate how enum values are marshaled in map fields vs normal fields in the grpc gateway runtime. Look at runtime/marshal json.go and the generated code for map fields. Check if the inconsistency is caused by different serialization paths. Review the protoc gen grpc gateway code generation for map entries. The issue asks whether this behavior is intended, so also check project maintainer comments or related discussions.