Add parser and swagger support for enum, no gengateway yet #108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds enum feature to parser and gen-swagger.
But no gen-grpc-gateway/gengateway yet.
One of problems is enum json encoding.
proto3 spec says enum should be encoded using string name.
However, since golang/protobuf generated codes have no MarshalJSON/UnmarshalJSON methods, it is encoded as a int, even if proto.Unmarshal/MarshalJSONEnum methods exist.
So json.Unmarshal on request will cause error if string name value is provided.
Note that Swagger support in this change uses string name as spec.
Refs: https://developers.google.com/protocol-buffers/docs/proto3#json