← All changes
|
includes/sdk/google/google/protobuf/src/Google/Protobuf/Any.php
+22
-16
1.0.1
→
1.4.2
View file →
| @@ -1,13 +1,14 @@ | ||
| 1 | 1 | <?php |
| 2 | 2 | |
| 3 | 3 | # Generated by the protocol buffer compiler. DO NOT EDIT! |
| 4 | +# NO CHECKED-IN PROTOBUF GENCODE | |
| 4 | 5 | # source: google/protobuf/any.proto |
| 5 | -namespace Dudlewebs\WPMCS\Google\Protobuf; | |
| 6 | +namespace Dudlewebs\WPMCS\GCP\Google\Protobuf; | |
| 6 | 7 | |
| 7 | -use Dudlewebs\WPMCS\Google\Protobuf\Internal\GPBType; | |
| 8 | -use Dudlewebs\WPMCS\Google\Protobuf\Internal\RepeatedField; | |
| 9 | -use Dudlewebs\WPMCS\Google\Protobuf\Internal\GPBUtil; | |
| 8 | +use Dudlewebs\WPMCS\GCP\Google\Protobuf\Internal\GPBType; | |
| 9 | +use Dudlewebs\WPMCS\GCP\Google\Protobuf\Internal\GPBUtil; | |
| 10 | +use Dudlewebs\WPMCS\GCP\Google\Protobuf\RepeatedField; | |
| 10 | 11 | /** |
| 11 | 12 | * `Any` contains an arbitrary serialized protocol buffer message along with a |
| 12 | 13 | * URL that describes the type of the serialized message. |
| 13 | 14 | * Protobuf library provides support to pack/unpack Any values in the form |
| @@ -30,9 +31,9 @@ | ||
| 30 | 31 | * // or ... |
| 31 | 32 | * if (any.isSameTypeAs(Foo.getDefaultInstance())) { |
| 32 | 33 | * foo = any.unpack(Foo.getDefaultInstance()); |
| 33 | 34 | * } |
| 34 | - * Example 3: Pack and unpack a message in Python. | |
| 35 | + * Example 3: Pack and unpack a message in Python. | |
| 35 | 36 | * foo = Foo(...) |
| 36 | 37 | * any = Any() |
| 37 | 38 | * any.Pack(foo) |
| 38 | 39 | * ... |
| @@ -38,9 +39,9 @@ | ||
| 38 | 39 | * ... |
| 39 | 40 | * if any.Is(Foo.DESCRIPTOR): |
| 40 | 41 | * any.Unpack(foo) |
| 41 | 42 | * ... |
| 42 | - * Example 4: Pack and unpack a message in Go | |
| 43 | + * Example 4: Pack and unpack a message in Go | |
| 43 | 44 | * foo := &pb.Foo{...} |
| 44 | 45 | * any, err := anypb.New(foo) |
| 45 | 46 | * if err != nil { |
| 46 | 47 | * ... |
| @@ -55,11 +56,12 @@ | ||
| 55 | 56 | * methods only use the fully qualified type name after the last '/' |
| 56 | 57 | * in the type URL, for example "foo.bar.com/x/y.z" will yield type |
| 57 | 58 | * name "y.z". |
| 58 | 59 | * JSON |
| 60 | + * ==== | |
| 59 | 61 | * The JSON representation of an `Any` value uses the regular |
| 60 | 62 | * representation of the deserialized, embedded message, with an |
| 61 | - * additional field `@type` which contains the type URL. Example: | |
| 63 | + * additional field `\@type` which contains the type URL. Example: | |
| 62 | 64 | * package google.profile; |
| 63 | 65 | * message Person { |
| 64 | 66 | * string first_name = 1; |
| 65 | 67 | * string last_name = 2; |
| @@ -64,24 +66,24 @@ | ||
| 64 | 66 | * string first_name = 1; |
| 65 | 67 | * string last_name = 2; |
| 66 | 68 | * } |
| 67 | 69 | * { |
| 68 | - * "@type": "type.googleapis.com/google.profile.Person", | |
| 70 | + * "\@type": "type.googleapis.com/google.profile.Person", | |
| 69 | 71 | * "firstName": <string>, |
| 70 | 72 | * "lastName": <string> |
| 71 | 73 | * } |
| 72 | 74 | * If the embedded message type is well-known and has a custom JSON |
| 73 | 75 | * representation, that representation will be embedded adding a field |
| 74 | - * `value` which holds the custom JSON in addition to the `@type` | |
| 76 | + * `value` which holds the custom JSON in addition to the `\@type` | |
| 75 | 77 | * field. Example (for message [google.protobuf.Duration][]): |
| 76 | 78 | * { |
| 77 | - * "@type": "type.googleapis.com/google.protobuf.Duration", | |
| 79 | + * "\@type": "type.googleapis.com/google.protobuf.Duration", | |
| 78 | 80 | * "value": "1.212s" |
| 79 | 81 | * } |
| 80 | 82 | * |
| 81 | 83 | * Generated from protobuf message <code>google.protobuf.Any</code> |
| 82 | 84 | */ |
| 83 | -class Any extends \Dudlewebs\WPMCS\Google\Protobuf\Internal\AnyBase | |
| 85 | +class Any extends \Dudlewebs\WPMCS\GCP\Google\Protobuf\Internal\AnyBase | |
| 84 | 86 | { |
| 85 | 87 | /** |
| 86 | 88 | * A URL/resource name that uniquely identifies the type of the serialized |
| 87 | 89 | * protocol buffer message. This string must contain at least |
| @@ -102,9 +104,10 @@ | ||
| 102 | 104 | * on changes to types. (Use versioned type names to manage |
| 103 | 105 | * breaking changes.) |
| 104 | 106 | * Note: this functionality is not currently available in the official |
| 105 | 107 | * protobuf release, and it is not used for type URLs beginning with |
| 106 | - * type.googleapis.com. | |
| 108 | + * type.googleapis.com. As of May 2023, there are no widely used type server | |
| 109 | + * implementations and no plans to implement one. | |
| 107 | 110 | * Schemes other than `http`, `https` (or the empty scheme) might be |
| 108 | 111 | * used with implementation specific semantics. |
| 109 | 112 | * |
| 110 | 113 | * Generated from protobuf field <code>string type_url = 1;</code> |
| @@ -142,9 +145,10 @@ | ||
| 142 | 145 | * on changes to types. (Use versioned type names to manage |
| 143 | 146 | * breaking changes.) |
| 144 | 147 | * Note: this functionality is not currently available in the official |
| 145 | 148 | * protobuf release, and it is not used for type URLs beginning with |
| 146 | - * type.googleapis.com. | |
| 149 | + * type.googleapis.com. As of May 2023, there are no widely used type server | |
| 150 | + * implementations and no plans to implement one. | |
| 147 | 151 | * Schemes other than `http`, `https` (or the empty scheme) might be |
| 148 | 152 | * used with implementation specific semantics. |
| 149 | 153 | * @type string $value |
| 150 | 154 | * Must be a valid serialized protocol buffer of the above specified type. |
| @@ -151,9 +155,9 @@ | ||
| 151 | 155 | * } |
| 152 | 156 | */ |
| 153 | 157 | public function __construct($data = NULL) |
| 154 | 158 | { |
| 155 | - \Dudlewebs\WPMCS\GPBMetadata\Google\Protobuf\Any::initOnce(); | |
| 159 | + \Dudlewebs\WPMCS\GCP\GPBMetadata\Google\Protobuf\Any::initOnce(); | |
| 156 | 160 | parent::__construct($data); |
| 157 | 161 | } |
| 158 | 162 | /** |
| 159 | 163 | * A URL/resource name that uniquely identifies the type of the serialized |
| @@ -175,9 +179,10 @@ | ||
| 175 | 179 | * on changes to types. (Use versioned type names to manage |
| 176 | 180 | * breaking changes.) |
| 177 | 181 | * Note: this functionality is not currently available in the official |
| 178 | 182 | * protobuf release, and it is not used for type URLs beginning with |
| 179 | - * type.googleapis.com. | |
| 183 | + * type.googleapis.com. As of May 2023, there are no widely used type server | |
| 184 | + * implementations and no plans to implement one. | |
| 180 | 185 | * Schemes other than `http`, `https` (or the empty scheme) might be |
| 181 | 186 | * used with implementation specific semantics. |
| 182 | 187 | * |
| 183 | 188 | * Generated from protobuf field <code>string type_url = 1;</code> |
| @@ -207,9 +212,10 @@ | ||
| 207 | 212 | * on changes to types. (Use versioned type names to manage |
| 208 | 213 | * breaking changes.) |
| 209 | 214 | * Note: this functionality is not currently available in the official |
| 210 | 215 | * protobuf release, and it is not used for type URLs beginning with |
| 211 | - * type.googleapis.com. | |
| 216 | + * type.googleapis.com. As of May 2023, there are no widely used type server | |
| 217 | + * implementations and no plans to implement one. | |
| 212 | 218 | * Schemes other than `http`, `https` (or the empty scheme) might be |
| 213 | 219 | * used with implementation specific semantics. |
| 214 | 220 | * |
| 215 | 221 | * Generated from protobuf field <code>string type_url = 1;</code> |