We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
protobuf.js version: 6.4.5
Custom option are not correctly parsed when using TextFormat definition
Given this proto :
syntax = "proto3"; package test; import "google/protobuf/descriptor.proto"; message MyOptions { string a = 1; string b = 2; } extend google.protobuf.FieldOptions { MyOptions my_options = 50000; } message Test { string value = 1 [(my_options) = { a: "foo" b: "bar" }]; }
Will result in :
{ '(my_options).a': 'foo', '(my_options).a.b': 'bar' }
Expected :
{ '(my_options).a': 'foo', '(my_options).b': 'bar' }
The text was updated successfully, but these errors were encountered:
As a workaround, protobuf syntax perfectly works :
message Test { string value = 1 [(my_options).a = "foo", (my_options).b = "bar"]; }
Result :
Sorry, something went wrong.
7e57f4c
No branches or pull requests
protobuf.js version: 6.4.5
Custom option are not correctly parsed when using TextFormat definition
Given this proto :
Will result in :
Expected :
The text was updated successfully, but these errors were encountered: