| <?php | |
| # Generated by the protocol buffer compiler. DO NOT EDIT! | |
| # NO CHECKED-IN PROTOBUF GENCODE | |
| # source: google/protobuf/descriptor.proto | |
| namespace Google\Protobuf\Internal\SourceCodeInfo; | |
| use Google\Protobuf\Internal\GPBType; | |
| use Google\Protobuf\Internal\GPBWire; | |
| use Google\Protobuf\Internal\InputStream; | |
| use Google\Protobuf\Internal\GPBUtil; | |
| use Google\Protobuf\RepeatedField; | |
| /** | |
| * Generated from protobuf message <code>google.protobuf.SourceCodeInfo.Location</code> | |
| */ | |
| class Location extends \Google\Protobuf\Internal\Message | |
| { | |
| /** | |
| * Identifies which part of the FileDescriptorProto was defined at this | |
| * location. | |
| * Each element is a field number or an index. They form a path from | |
| * the root FileDescriptorProto to the place where the definition appears. | |
| * For example, this path: | |
| * [ 4, 3, 2, 7, 1 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .field(7) // 2, 7 | |
| * .name() // 1 | |
| * This is because FileDescriptorProto.message_type has field number 4: | |
| * repeated DescriptorProto message_type = 4; | |
| * and DescriptorProto.field has field number 2: | |
| * repeated FieldDescriptorProto field = 2; | |
| * and FieldDescriptorProto.name has field number 1: | |
| * optional string name = 1; | |
| * Thus, the above path gives the location of a field name. If we removed | |
| * the last element: | |
| * [ 4, 3, 2, 7 ] | |
| * this path refers to the whole field declaration (from the beginning | |
| * of the label to the terminating semicolon). | |
| * For options, the path refers to the interpreted option in the descriptor. | |
| * E.g., for a custom option `(my_opt) = "foo"` on a message using extension | |
| * number 10101, the path is: | |
| * [ 4, 3, 7, 10101 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .options() // 7 | |
| * .my_opt() // 10101 | |
| * Option parts, e.g. name and value are also appended using field numbers | |
| * from `UninterpretedOption`, which deviates from the actual | |
| * FileDescriptorProto path and uses negative values. | |
| * E.g., for `(my_opt) = "foo"` the name `(my_opt)` is: | |
| * [ 4, 3, 7, 10101, -2 ] | |
| * where -2 is negative of `UninterpretedOption.name`. | |
| * The value "foo" is: | |
| * [ 4, 3, 7, 10101, -7 ] | |
| * where -7 is the negative of `UninterpretedOption.string_value`. | |
| * For complex options (e.g., "(my_opt) = {a: 100}"), the path | |
| * will include -UninterpretedOption.aggregate_value (field number -8) as a | |
| * marker for each level of nesting. | |
| * For example, given: | |
| * option (my_opt) = {a: 100}; | |
| * The path for the `a` identifier would look like: | |
| * [ 4, 3, 7, 10101, -8, 1, -2 ] | |
| * And for the value 100: | |
| * [ 4, 3, 7, 10101, -8, 1, -4 ] | |
| * Where: | |
| * -8: UninterpretedOption.aggregate_value marker | |
| * 1: The field number of "a" inside "my_opt" | |
| * -2: UninterpretedOption.name | |
| * -4: UninterpretedOption.positive_int_value | |
| * We use negative values for UninterpretedOption due to keep it backward | |
| * compatible with pre-existing undocumented behavior where options using | |
| * dot-notation (e.g. `(my_opt).a = 100`) also produce a path like | |
| * [ 4, 3, 7, 10101, 1] that spans the entire option. | |
| * | |
| * Generated from protobuf field <code>repeated int32 path = 1 [packed = true];</code> | |
| */ | |
| private $path; | |
| /** | |
| * Always has exactly three or four elements: start line, start column, | |
| * end line (optional, otherwise assumed same as start line), end column. | |
| * These are packed into a single field for efficiency. Note that line | |
| * and column numbers are zero-based -- typically you will want to add | |
| * 1 to each before displaying to a user. | |
| * | |
| * Generated from protobuf field <code>repeated int32 span = 2 [packed = true];</code> | |
| */ | |
| private $span; | |
| /** | |
| * If this SourceCodeInfo represents a complete declaration, these are any | |
| * comments appearing before and after the declaration which appear to be | |
| * attached to the declaration. | |
| * A series of line comments appearing on consecutive lines, with no other | |
| * tokens appearing on those lines, will be treated as a single comment. | |
| * leading_detached_comments will keep paragraphs of comments that appear | |
| * before (but not connected to) the current element. Each paragraph, | |
| * separated by empty lines, will be one comment element in the repeated | |
| * field. | |
| * Only the comment content is provided; comment markers (e.g. //) are | |
| * stripped out. For block comments, leading whitespace and an asterisk | |
| * will be stripped from the beginning of each line other than the first. | |
| * Newlines are included in the output. | |
| * Examples: | |
| * optional int32 foo = 1; // Comment attached to foo. | |
| * // Comment attached to bar. | |
| * optional int32 bar = 2; | |
| * optional string baz = 3; | |
| * // Comment attached to baz. | |
| * // Another line attached to baz. | |
| * // Comment attached to moo. | |
| * // | |
| * // Another line attached to moo. | |
| * optional double moo = 4; | |
| * // Detached comment for corge. This is not leading or trailing comments | |
| * // to moo or corge because there are blank lines separating it from | |
| * // both. | |
| * // Detached comment for corge paragraph 2. | |
| * optional string corge = 5; | |
| * /* Block comment attached | |
| * * to corge. Leading asterisks | |
| * * will be removed. {@*} | |
| * /* Block comment attached to | |
| * * grault. {@*} | |
| * optional int32 grault = 6; | |
| * // ignored detached comments. | |
| * | |
| * Generated from protobuf field <code>optional string leading_comments = 3;</code> | |
| */ | |
| protected $leading_comments = null; | |
| /** | |
| * Generated from protobuf field <code>optional string trailing_comments = 4;</code> | |
| */ | |
| protected $trailing_comments = null; | |
| /** | |
| * Generated from protobuf field <code>repeated string leading_detached_comments = 6;</code> | |
| */ | |
| private $leading_detached_comments; | |
| /** | |
| * Constructor. | |
| * | |
| * @param array $data { | |
| * Optional. Data for populating the Message object. | |
| * | |
| * @type int[] $path | |
| * Identifies which part of the FileDescriptorProto was defined at this | |
| * location. | |
| * Each element is a field number or an index. They form a path from | |
| * the root FileDescriptorProto to the place where the definition appears. | |
| * For example, this path: | |
| * [ 4, 3, 2, 7, 1 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .field(7) // 2, 7 | |
| * .name() // 1 | |
| * This is because FileDescriptorProto.message_type has field number 4: | |
| * repeated DescriptorProto message_type = 4; | |
| * and DescriptorProto.field has field number 2: | |
| * repeated FieldDescriptorProto field = 2; | |
| * and FieldDescriptorProto.name has field number 1: | |
| * optional string name = 1; | |
| * Thus, the above path gives the location of a field name. If we removed | |
| * the last element: | |
| * [ 4, 3, 2, 7 ] | |
| * this path refers to the whole field declaration (from the beginning | |
| * of the label to the terminating semicolon). | |
| * For options, the path refers to the interpreted option in the descriptor. | |
| * E.g., for a custom option `(my_opt) = "foo"` on a message using extension | |
| * number 10101, the path is: | |
| * [ 4, 3, 7, 10101 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .options() // 7 | |
| * .my_opt() // 10101 | |
| * Option parts, e.g. name and value are also appended using field numbers | |
| * from `UninterpretedOption`, which deviates from the actual | |
| * FileDescriptorProto path and uses negative values. | |
| * E.g., for `(my_opt) = "foo"` the name `(my_opt)` is: | |
| * [ 4, 3, 7, 10101, -2 ] | |
| * where -2 is negative of `UninterpretedOption.name`. | |
| * The value "foo" is: | |
| * [ 4, 3, 7, 10101, -7 ] | |
| * where -7 is the negative of `UninterpretedOption.string_value`. | |
| * For complex options (e.g., "(my_opt) = {a: 100}"), the path | |
| * will include -UninterpretedOption.aggregate_value (field number -8) as a | |
| * marker for each level of nesting. | |
| * For example, given: | |
| * option (my_opt) = {a: 100}; | |
| * The path for the `a` identifier would look like: | |
| * [ 4, 3, 7, 10101, -8, 1, -2 ] | |
| * And for the value 100: | |
| * [ 4, 3, 7, 10101, -8, 1, -4 ] | |
| * Where: | |
| * -8: UninterpretedOption.aggregate_value marker | |
| * 1: The field number of "a" inside "my_opt" | |
| * -2: UninterpretedOption.name | |
| * -4: UninterpretedOption.positive_int_value | |
| * We use negative values for UninterpretedOption due to keep it backward | |
| * compatible with pre-existing undocumented behavior where options using | |
| * dot-notation (e.g. `(my_opt).a = 100`) also produce a path like | |
| * [ 4, 3, 7, 10101, 1] that spans the entire option. | |
| * @type int[] $span | |
| * Always has exactly three or four elements: start line, start column, | |
| * end line (optional, otherwise assumed same as start line), end column. | |
| * These are packed into a single field for efficiency. Note that line | |
| * and column numbers are zero-based -- typically you will want to add | |
| * 1 to each before displaying to a user. | |
| * @type string $leading_comments | |
| * If this SourceCodeInfo represents a complete declaration, these are any | |
| * comments appearing before and after the declaration which appear to be | |
| * attached to the declaration. | |
| * A series of line comments appearing on consecutive lines, with no other | |
| * tokens appearing on those lines, will be treated as a single comment. | |
| * leading_detached_comments will keep paragraphs of comments that appear | |
| * before (but not connected to) the current element. Each paragraph, | |
| * separated by empty lines, will be one comment element in the repeated | |
| * field. | |
| * Only the comment content is provided; comment markers (e.g. //) are | |
| * stripped out. For block comments, leading whitespace and an asterisk | |
| * will be stripped from the beginning of each line other than the first. | |
| * Newlines are included in the output. | |
| * Examples: | |
| * optional int32 foo = 1; // Comment attached to foo. | |
| * // Comment attached to bar. | |
| * optional int32 bar = 2; | |
| * optional string baz = 3; | |
| * // Comment attached to baz. | |
| * // Another line attached to baz. | |
| * // Comment attached to moo. | |
| * // | |
| * // Another line attached to moo. | |
| * optional double moo = 4; | |
| * // Detached comment for corge. This is not leading or trailing comments | |
| * // to moo or corge because there are blank lines separating it from | |
| * // both. | |
| * // Detached comment for corge paragraph 2. | |
| * optional string corge = 5; | |
| * /* Block comment attached | |
| * * to corge. Leading asterisks | |
| * * will be removed. {@*} | |
| * /* Block comment attached to | |
| * * grault. {@*} | |
| * optional int32 grault = 6; | |
| * // ignored detached comments. | |
| * @type string $trailing_comments | |
| * @type string[] $leading_detached_comments | |
| * } | |
| */ | |
| public function __construct($data = null) | |
| { | |
| \GPBMetadata\Google\Protobuf\Internal\Descriptor::initOnce(); | |
| parent::__construct($data); | |
| } | |
| /** | |
| * Identifies which part of the FileDescriptorProto was defined at this | |
| * location. | |
| * Each element is a field number or an index. They form a path from | |
| * the root FileDescriptorProto to the place where the definition appears. | |
| * For example, this path: | |
| * [ 4, 3, 2, 7, 1 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .field(7) // 2, 7 | |
| * .name() // 1 | |
| * This is because FileDescriptorProto.message_type has field number 4: | |
| * repeated DescriptorProto message_type = 4; | |
| * and DescriptorProto.field has field number 2: | |
| * repeated FieldDescriptorProto field = 2; | |
| * and FieldDescriptorProto.name has field number 1: | |
| * optional string name = 1; | |
| * Thus, the above path gives the location of a field name. If we removed | |
| * the last element: | |
| * [ 4, 3, 2, 7 ] | |
| * this path refers to the whole field declaration (from the beginning | |
| * of the label to the terminating semicolon). | |
| * For options, the path refers to the interpreted option in the descriptor. | |
| * E.g., for a custom option `(my_opt) = "foo"` on a message using extension | |
| * number 10101, the path is: | |
| * [ 4, 3, 7, 10101 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .options() // 7 | |
| * .my_opt() // 10101 | |
| * Option parts, e.g. name and value are also appended using field numbers | |
| * from `UninterpretedOption`, which deviates from the actual | |
| * FileDescriptorProto path and uses negative values. | |
| * E.g., for `(my_opt) = "foo"` the name `(my_opt)` is: | |
| * [ 4, 3, 7, 10101, -2 ] | |
| * where -2 is negative of `UninterpretedOption.name`. | |
| * The value "foo" is: | |
| * [ 4, 3, 7, 10101, -7 ] | |
| * where -7 is the negative of `UninterpretedOption.string_value`. | |
| * For complex options (e.g., "(my_opt) = {a: 100}"), the path | |
| * will include -UninterpretedOption.aggregate_value (field number -8) as a | |
| * marker for each level of nesting. | |
| * For example, given: | |
| * option (my_opt) = {a: 100}; | |
| * The path for the `a` identifier would look like: | |
| * [ 4, 3, 7, 10101, -8, 1, -2 ] | |
| * And for the value 100: | |
| * [ 4, 3, 7, 10101, -8, 1, -4 ] | |
| * Where: | |
| * -8: UninterpretedOption.aggregate_value marker | |
| * 1: The field number of "a" inside "my_opt" | |
| * -2: UninterpretedOption.name | |
| * -4: UninterpretedOption.positive_int_value | |
| * We use negative values for UninterpretedOption due to keep it backward | |
| * compatible with pre-existing undocumented behavior where options using | |
| * dot-notation (e.g. `(my_opt).a = 100`) also produce a path like | |
| * [ 4, 3, 7, 10101, 1] that spans the entire option. | |
| * | |
| * Generated from protobuf field <code>repeated int32 path = 1 [packed = true];</code> | |
| * @return RepeatedField<int> | |
| */ | |
| public function getPath() | |
| { | |
| return $this->path; | |
| } | |
| /** | |
| * Identifies which part of the FileDescriptorProto was defined at this | |
| * location. | |
| * Each element is a field number or an index. They form a path from | |
| * the root FileDescriptorProto to the place where the definition appears. | |
| * For example, this path: | |
| * [ 4, 3, 2, 7, 1 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .field(7) // 2, 7 | |
| * .name() // 1 | |
| * This is because FileDescriptorProto.message_type has field number 4: | |
| * repeated DescriptorProto message_type = 4; | |
| * and DescriptorProto.field has field number 2: | |
| * repeated FieldDescriptorProto field = 2; | |
| * and FieldDescriptorProto.name has field number 1: | |
| * optional string name = 1; | |
| * Thus, the above path gives the location of a field name. If we removed | |
| * the last element: | |
| * [ 4, 3, 2, 7 ] | |
| * this path refers to the whole field declaration (from the beginning | |
| * of the label to the terminating semicolon). | |
| * For options, the path refers to the interpreted option in the descriptor. | |
| * E.g., for a custom option `(my_opt) = "foo"` on a message using extension | |
| * number 10101, the path is: | |
| * [ 4, 3, 7, 10101 ] | |
| * refers to: | |
| * file.message_type(3) // 4, 3 | |
| * .options() // 7 | |
| * .my_opt() // 10101 | |
| * Option parts, e.g. name and value are also appended using field numbers | |
| * from `UninterpretedOption`, which deviates from the actual | |
| * FileDescriptorProto path and uses negative values. | |
| * E.g., for `(my_opt) = "foo"` the name `(my_opt)` is: | |
| * [ 4, 3, 7, 10101, -2 ] | |
| * where -2 is negative of `UninterpretedOption.name`. | |
| * The value "foo" is: | |
| * [ 4, 3, 7, 10101, -7 ] | |
| * where -7 is the negative of `UninterpretedOption.string_value`. | |
| * For complex options (e.g., "(my_opt) = {a: 100}"), the path | |
| * will include -UninterpretedOption.aggregate_value (field number -8) as a | |
| * marker for each level of nesting. | |
| * For example, given: | |
| * option (my_opt) = {a: 100}; | |
| * The path for the `a` identifier would look like: | |
| * [ 4, 3, 7, 10101, -8, 1, -2 ] | |
| * And for the value 100: | |
| * [ 4, 3, 7, 10101, -8, 1, -4 ] | |
| * Where: | |
| * -8: UninterpretedOption.aggregate_value marker | |
| * 1: The field number of "a" inside "my_opt" | |
| * -2: UninterpretedOption.name | |
| * -4: UninterpretedOption.positive_int_value | |
| * We use negative values for UninterpretedOption due to keep it backward | |
| * compatible with pre-existing undocumented behavior where options using | |
| * dot-notation (e.g. `(my_opt).a = 100`) also produce a path like | |
| * [ 4, 3, 7, 10101, 1] that spans the entire option. | |
| * | |
| * Generated from protobuf field <code>repeated int32 path = 1 [packed = true];</code> | |
| * @param int[] $var | |
| * @return $this | |
| */ | |
| public function setPath(array|RepeatedField $var) | |
| { | |
| $arr = GPBUtil::checkRepeatedField($var, \Google\Protobuf\Internal\GPBType::INT32); | |
| $this->path = $arr; | |
| return $this; | |
| } | |
| /** | |
| * Always has exactly three or four elements: start line, start column, | |
| * end line (optional, otherwise assumed same as start line), end column. | |
| * These are packed into a single field for efficiency. Note that line | |
| * and column numbers are zero-based -- typically you will want to add | |
| * 1 to each before displaying to a user. | |
| * | |
| * Generated from protobuf field <code>repeated int32 span = 2 [packed = true];</code> | |
| * @return RepeatedField<int> | |
| */ | |
| public function getSpan() | |
| { | |
| return $this->span; | |
| } | |
| /** | |
| * Always has exactly three or four elements: start line, start column, | |
| * end line (optional, otherwise assumed same as start line), end column. | |
| * These are packed into a single field for efficiency. Note that line | |
| * and column numbers are zero-based -- typically you will want to add | |
| * 1 to each before displaying to a user. | |
| * | |
| * Generated from protobuf field <code>repeated int32 span = 2 [packed = true];</code> | |
| * @param int[] $var | |
| * @return $this | |
| */ | |
| public function setSpan(array|RepeatedField $var) | |
| { | |
| $arr = GPBUtil::checkRepeatedField($var, \Google\Protobuf\Internal\GPBType::INT32); | |
| $this->span = $arr; | |
| return $this; | |
| } | |
| /** | |
| * If this SourceCodeInfo represents a complete declaration, these are any | |
| * comments appearing before and after the declaration which appear to be | |
| * attached to the declaration. | |
| * A series of line comments appearing on consecutive lines, with no other | |
| * tokens appearing on those lines, will be treated as a single comment. | |
| * leading_detached_comments will keep paragraphs of comments that appear | |
| * before (but not connected to) the current element. Each paragraph, | |
| * separated by empty lines, will be one comment element in the repeated | |
| * field. | |
| * Only the comment content is provided; comment markers (e.g. //) are | |
| * stripped out. For block comments, leading whitespace and an asterisk | |
| * will be stripped from the beginning of each line other than the first. | |
| * Newlines are included in the output. | |
| * Examples: | |
| * optional int32 foo = 1; // Comment attached to foo. | |
| * // Comment attached to bar. | |
| * optional int32 bar = 2; | |
| * optional string baz = 3; | |
| * // Comment attached to baz. | |
| * // Another line attached to baz. | |
| * // Comment attached to moo. | |
| * // | |
| * // Another line attached to moo. | |
| * optional double moo = 4; | |
| * // Detached comment for corge. This is not leading or trailing comments | |
| * // to moo or corge because there are blank lines separating it from | |
| * // both. | |
| * // Detached comment for corge paragraph 2. | |
| * optional string corge = 5; | |
| * /* Block comment attached | |
| * * to corge. Leading asterisks | |
| * * will be removed. {@*} | |
| * /* Block comment attached to | |
| * * grault. {@*} | |
| * optional int32 grault = 6; | |
| * // ignored detached comments. | |
| * | |
| * Generated from protobuf field <code>optional string leading_comments = 3;</code> | |
| * @return string | |
| */ | |
| public function getLeadingComments() | |
| { | |
| return isset($this->leading_comments) ? $this->leading_comments : ''; | |
| } | |
| public function hasLeadingComments() | |
| { | |
| return isset($this->leading_comments); | |
| } | |
| public function clearLeadingComments() | |
| { | |
| unset($this->leading_comments); | |
| } | |
| /** | |
| * If this SourceCodeInfo represents a complete declaration, these are any | |
| * comments appearing before and after the declaration which appear to be | |
| * attached to the declaration. | |
| * A series of line comments appearing on consecutive lines, with no other | |
| * tokens appearing on those lines, will be treated as a single comment. | |
| * leading_detached_comments will keep paragraphs of comments that appear | |
| * before (but not connected to) the current element. Each paragraph, | |
| * separated by empty lines, will be one comment element in the repeated | |
| * field. | |
| * Only the comment content is provided; comment markers (e.g. //) are | |
| * stripped out. For block comments, leading whitespace and an asterisk | |
| * will be stripped from the beginning of each line other than the first. | |
| * Newlines are included in the output. | |
| * Examples: | |
| * optional int32 foo = 1; // Comment attached to foo. | |
| * // Comment attached to bar. | |
| * optional int32 bar = 2; | |
| * optional string baz = 3; | |
| * // Comment attached to baz. | |
| * // Another line attached to baz. | |
| * // Comment attached to moo. | |
| * // | |
| * // Another line attached to moo. | |
| * optional double moo = 4; | |
| * // Detached comment for corge. This is not leading or trailing comments | |
| * // to moo or corge because there are blank lines separating it from | |
| * // both. | |
| * // Detached comment for corge paragraph 2. | |
| * optional string corge = 5; | |
| * /* Block comment attached | |
| * * to corge. Leading asterisks | |
| * * will be removed. {@*} | |
| * /* Block comment attached to | |
| * * grault. {@*} | |
| * optional int32 grault = 6; | |
| * // ignored detached comments. | |
| * | |
| * Generated from protobuf field <code>optional string leading_comments = 3;</code> | |
| * @param string $var | |
| * @return $this | |
| */ | |
| public function setLeadingComments(string $var) | |
| { | |
| GPBUtil::checkString($var, true); | |
| $this->leading_comments = $var; | |
| return $this; | |
| } | |
| /** | |
| * Generated from protobuf field <code>optional string trailing_comments = 4;</code> | |
| * @return string | |
| */ | |
| public function getTrailingComments() | |
| { | |
| return isset($this->trailing_comments) ? $this->trailing_comments : ''; | |
| } | |
| public function hasTrailingComments() | |
| { | |
| return isset($this->trailing_comments); | |
| } | |
| public function clearTrailingComments() | |
| { | |
| unset($this->trailing_comments); | |
| } | |
| /** | |
| * Generated from protobuf field <code>optional string trailing_comments = 4;</code> | |
| * @param string $var | |
| * @return $this | |
| */ | |
| public function setTrailingComments(string $var) | |
| { | |
| GPBUtil::checkString($var, true); | |
| $this->trailing_comments = $var; | |
| return $this; | |
| } | |
| /** | |
| * Generated from protobuf field <code>repeated string leading_detached_comments = 6;</code> | |
| * @return RepeatedField<string> | |
| */ | |
| public function getLeadingDetachedComments() | |
| { | |
| return $this->leading_detached_comments; | |
| } | |
| /** | |
| * Generated from protobuf field <code>repeated string leading_detached_comments = 6;</code> | |
| * @param string[] $var | |
| * @return $this | |
| */ | |
| public function setLeadingDetachedComments(array|RepeatedField $var) | |
| { | |
| $arr = GPBUtil::checkRepeatedField($var, \Google\Protobuf\Internal\GPBType::STRING); | |
| $this->leading_detached_comments = $arr; | |
| return $this; | |
| } | |
| } | |