Commit af8b91b8 authored by Yilun Chong's avatar Yilun Chong

fix csharp by regenerate descriptor

parent 429d2ae1
...@@ -4996,7 +4996,7 @@ namespace Google.Protobuf.Reflection { ...@@ -4996,7 +4996,7 @@ namespace Google.Protobuf.Reflection {
/// ///
/// Implementations may choose not to generate the map_entry=true message, but /// Implementations may choose not to generate the map_entry=true message, but
/// use a native map in the target language to hold the keys and values. /// use a native map in the target language to hold the keys and values.
/// The reflection APIs in such implementions still need to work as /// The reflection APIs in such implementations still need to work as
/// if the field is a repeated message field. /// if the field is a repeated message field.
/// ///
/// NOTE: Do not set the option in .proto files. Always use the maps syntax /// NOTE: Do not set the option in .proto files. Always use the maps syntax
...@@ -7238,7 +7238,7 @@ namespace Google.Protobuf.Reflection { ...@@ -7238,7 +7238,7 @@ namespace Google.Protobuf.Reflection {
/// beginning of the "extend" block and is shared by all extensions within /// beginning of the "extend" block and is shared by all extensions within
/// the block. /// the block.
/// - Just because a location's span is a subset of some other location's span /// - Just because a location's span is a subset of some other location's span
/// does not mean that it is a descendent. For example, a "group" defines /// does not mean that it is a descendant. For example, a "group" defines
/// both a type and a field in a single declaration. Thus, the locations /// both a type and a field in a single declaration. Thus, the locations
/// corresponding to the type and field and their components will overlap. /// corresponding to the type and field and their components will overlap.
/// - Code which tries to interpret locations should probably be designed to /// - Code which tries to interpret locations should probably be designed to
......
...@@ -70,7 +70,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message ...@@ -70,7 +70,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message
* repeated MapFieldEntry map_field = 1; * repeated MapFieldEntry map_field = 1;
* Implementations may choose not to generate the map_entry=true message, but * Implementations may choose not to generate the map_entry=true message, but
* use a native map in the target language to hold the keys and values. * use a native map in the target language to hold the keys and values.
* The reflection APIs in such implementions still need to work as * The reflection APIs in such implementations still need to work as
* if the field is a repeated message field. * if the field is a repeated message field.
* NOTE: Do not set the option in .proto files. Always use the maps syntax * NOTE: Do not set the option in .proto files. Always use the maps syntax
* instead. The option should only be implicitly set by the proto compiler * instead. The option should only be implicitly set by the proto compiler
...@@ -133,7 +133,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message ...@@ -133,7 +133,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message
* repeated MapFieldEntry map_field = 1; * repeated MapFieldEntry map_field = 1;
* Implementations may choose not to generate the map_entry=true message, but * Implementations may choose not to generate the map_entry=true message, but
* use a native map in the target language to hold the keys and values. * use a native map in the target language to hold the keys and values.
* The reflection APIs in such implementions still need to work as * The reflection APIs in such implementations still need to work as
* if the field is a repeated message field. * if the field is a repeated message field.
* NOTE: Do not set the option in .proto files. Always use the maps syntax * NOTE: Do not set the option in .proto files. Always use the maps syntax
* instead. The option should only be implicitly set by the proto compiler * instead. The option should only be implicitly set by the proto compiler
...@@ -295,7 +295,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message ...@@ -295,7 +295,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message
* repeated MapFieldEntry map_field = 1; * repeated MapFieldEntry map_field = 1;
* Implementations may choose not to generate the map_entry=true message, but * Implementations may choose not to generate the map_entry=true message, but
* use a native map in the target language to hold the keys and values. * use a native map in the target language to hold the keys and values.
* The reflection APIs in such implementions still need to work as * The reflection APIs in such implementations still need to work as
* if the field is a repeated message field. * if the field is a repeated message field.
* NOTE: Do not set the option in .proto files. Always use the maps syntax * NOTE: Do not set the option in .proto files. Always use the maps syntax
* instead. The option should only be implicitly set by the proto compiler * instead. The option should only be implicitly set by the proto compiler
...@@ -323,7 +323,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message ...@@ -323,7 +323,7 @@ class MessageOptions extends \Google\Protobuf\Internal\Message
* repeated MapFieldEntry map_field = 1; * repeated MapFieldEntry map_field = 1;
* Implementations may choose not to generate the map_entry=true message, but * Implementations may choose not to generate the map_entry=true message, but
* use a native map in the target language to hold the keys and values. * use a native map in the target language to hold the keys and values.
* The reflection APIs in such implementions still need to work as * The reflection APIs in such implementations still need to work as
* if the field is a repeated message field. * if the field is a repeated message field.
* NOTE: Do not set the option in .proto files. Always use the maps syntax * NOTE: Do not set the option in .proto files. Always use the maps syntax
* instead. The option should only be implicitly set by the proto compiler * instead. The option should only be implicitly set by the proto compiler
......
...@@ -55,7 +55,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message ...@@ -55,7 +55,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message
* beginning of the "extend" block and is shared by all extensions within * beginning of the "extend" block and is shared by all extensions within
* the block. * the block.
* - Just because a location's span is a subset of some other location's span * - Just because a location's span is a subset of some other location's span
* does not mean that it is a descendent. For example, a "group" defines * does not mean that it is a descendant. For example, a "group" defines
* both a type and a field in a single declaration. Thus, the locations * both a type and a field in a single declaration. Thus, the locations
* corresponding to the type and field and their components will overlap. * corresponding to the type and field and their components will overlap.
* - Code which tries to interpret locations should probably be designed to * - Code which tries to interpret locations should probably be designed to
...@@ -109,7 +109,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message ...@@ -109,7 +109,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message
* beginning of the "extend" block and is shared by all extensions within * beginning of the "extend" block and is shared by all extensions within
* the block. * the block.
* - Just because a location's span is a subset of some other location's span * - Just because a location's span is a subset of some other location's span
* does not mean that it is a descendent. For example, a "group" defines * does not mean that it is a descendant. For example, a "group" defines
* both a type and a field in a single declaration. Thus, the locations * both a type and a field in a single declaration. Thus, the locations
* corresponding to the type and field and their components will overlap. * corresponding to the type and field and their components will overlap.
* - Code which tries to interpret locations should probably be designed to * - Code which tries to interpret locations should probably be designed to
...@@ -158,7 +158,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message ...@@ -158,7 +158,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message
* beginning of the "extend" block and is shared by all extensions within * beginning of the "extend" block and is shared by all extensions within
* the block. * the block.
* - Just because a location's span is a subset of some other location's span * - Just because a location's span is a subset of some other location's span
* does not mean that it is a descendent. For example, a "group" defines * does not mean that it is a descendant. For example, a "group" defines
* both a type and a field in a single declaration. Thus, the locations * both a type and a field in a single declaration. Thus, the locations
* corresponding to the type and field and their components will overlap. * corresponding to the type and field and their components will overlap.
* - Code which tries to interpret locations should probably be designed to * - Code which tries to interpret locations should probably be designed to
...@@ -209,7 +209,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message ...@@ -209,7 +209,7 @@ class SourceCodeInfo extends \Google\Protobuf\Internal\Message
* beginning of the "extend" block and is shared by all extensions within * beginning of the "extend" block and is shared by all extensions within
* the block. * the block.
* - Just because a location's span is a subset of some other location's span * - Just because a location's span is a subset of some other location's span
* does not mean that it is a descendent. For example, a "group" defines * does not mean that it is a descendant. For example, a "group" defines
* both a type and a field in a single declaration. Thus, the locations * both a type and a field in a single declaration. Thus, the locations
* corresponding to the type and field and their components will overlap. * corresponding to the type and field and their components will overlap.
* - Code which tries to interpret locations should probably be designed to * - Code which tries to interpret locations should probably be designed to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment