Closed hfjn closed 2 years ago
@hfjn That's nearly right! This parser conforms to the spec like enumValueOption = optionName "=" constant.
So that, the part around "{field_number: 101}" should be fullIdent | ( [ "-" | "+" ] intLit ) | ( [ "-" | "+" ] floatLit ) | strLit | boolLit.
To sum up, you can fix a line like below.
- REQUEST = 1 [(event_additional_data) = {field_number: 101}];
+ REQUEST = 1 [(event_additional_data) = "{field_number: 101}"];
[memo] This parser extends a rule regarding a field option beyond the spec to parse a grpc-gateway_a_bit_of_everything.proto.
Hi!
Awesome application, thanks for building this. I hit a minor issue today:
We have enums defined which have custom options pointing to another message for documentation purposes:
e.g. something like this
This fails during parsing with:
After checking the code I assume the enum type currently only supports String types?
Thanks!