Status Update
No update yet.
Comments
cg...@gmail.com
ku...@google.com
cg...@gmail.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
ku...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
cg...@gmail.com
An engineer should be able to take a look at the documentation screenshot and say if it's missing annotation or not.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Here in this document while explain default values example, doc mentions about annotation to get NULL for message_field_y.field_c but it doesn't document what annotation.
Attached a screenshot with highlight.
message SimpleMessage {
optional SubMessage message_field_x = 1;
optional SubMessage message_field_y = 2;
}
message SubMessage {
optional string field_a = 1;
optional string field_b = 2;
optional string field_c = 3;
repeated string field_d = 4;
repeated string field_e = 5;
}
Assume the following field values:
message_field_x isn't set.
message_field_y.field_a is set to "a".
message_field_y.field_b isn't set.
message_field_y.field_c isn't set.
message_field_y.field_d is set to ["d"].
message_field_y.field_e isn't set.
message_field_y.field_b "" (empty string) Field isn't set but parent message is set, so default value (empty string) is produced.
message_field_y.field_c NULL Field isn't set and annotation indicates to not use defaults.
What you expected to happen:
Missing documentation
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):