← All changes
|
includes/sdk/google/google/common-protos/src/Api/RoutingParameter.php
+18
-18
1.0.3
→
1.4.2
View file →
| @@ -1,19 +1,19 @@ | ||
| 1 | 1 | <?php |
| 2 | 2 | |
| 3 | 3 | # Generated by the protocol buffer compiler. DO NOT EDIT! |
| 4 | 4 | # source: google/api/routing.proto |
| 5 | -namespace Dudlewebs\WPMCS\Google\Api; | |
| 5 | +namespace Dudlewebs\WPMCS\GCP\Google\Api; | |
| 6 | 6 | |
| 7 | -use Dudlewebs\WPMCS\Google\Protobuf\Internal\GPBType; | |
| 8 | -use Dudlewebs\WPMCS\Google\Protobuf\Internal\RepeatedField; | |
| 9 | -use Dudlewebs\WPMCS\Google\Protobuf\Internal\GPBUtil; | |
| 7 | +use Dudlewebs\WPMCS\GCP\Google\Protobuf\Internal\GPBType; | |
| 8 | +use Dudlewebs\WPMCS\GCP\Google\Protobuf\Internal\GPBUtil; | |
| 9 | +use Dudlewebs\WPMCS\GCP\Google\Protobuf\RepeatedField; | |
| 10 | 10 | /** |
| 11 | 11 | * A projection from an input message to the GRPC or REST header. |
| 12 | 12 | * |
| 13 | 13 | * Generated from protobuf message <code>google.api.RoutingParameter</code> |
| 14 | 14 | */ |
| 15 | -class RoutingParameter extends \Dudlewebs\WPMCS\Google\Protobuf\Internal\Message | |
| 15 | +class RoutingParameter extends \Dudlewebs\WPMCS\GCP\Google\Protobuf\Internal\Message | |
| 16 | 16 | { |
| 17 | 17 | /** |
| 18 | 18 | * A request field to extract the header key-value pair from. |
| 19 | 19 | * |
| @@ -37,9 +37,9 @@ | ||
| 37 | 37 | * | -- This is the key name in the |
| 38 | 38 | * | | routing header. |
| 39 | 39 | * V | |
| 40 | 40 | * field: "table_name" v |
| 41 | - * path_template: "projects/*/{table_location=instances/*}/tables/*" | |
| 41 | + * path_template: "projects/{@*}{table_location=instances/*}/tables/*" | |
| 42 | 42 | * ^ ^ |
| 43 | 43 | * | | |
| 44 | 44 | * In the {} brackets is the pattern that -- | |
| 45 | 45 | * specifies what to extract from the | |
| @@ -48,13 +48,13 @@ | ||
| 48 | 48 | * The string in the field must match the whole pattern -- |
| 49 | 49 | * before brackets, inside brackets, after brackets. |
| 50 | 50 | * When looking at this specific example, we can see that: |
| 51 | 51 | * - A key-value pair with the key `table_location` |
| 52 | - * and the value matching `instances/*` should be added | |
| 52 | + * and the value matching `instances/*` should be added | |
| 53 | 53 | * to the x-goog-request-params routing header. |
| 54 | 54 | * - The value is extracted from the request message's `table_name` field |
| 55 | 55 | * if it matches the full pattern specified: |
| 56 | - * `projects/*/instances/*/tables/*`. | |
| 56 | + * `projects/{@*}instances/{@*}tables/*`. | |
| 57 | 57 | * **NB:** If the `path_template` field is not provided, the key name is |
| 58 | 58 | * equal to the field name, and the whole field should be sent as a value. |
| 59 | 59 | * This makes the pattern for the field and the value functionally equivalent |
| 60 | 60 | * to `**`, and the configuration |
| @@ -96,9 +96,9 @@ | ||
| 96 | 96 | * | -- This is the key name in the |
| 97 | 97 | * | | routing header. |
| 98 | 98 | * V | |
| 99 | 99 | * field: "table_name" v |
| 100 | - * path_template: "projects/*/{table_location=instances/*}/tables/*" | |
| 100 | + * path_template: "projects/{@*}{table_location=instances/*}/tables/*" | |
| 101 | 101 | * ^ ^ |
| 102 | 102 | * | | |
| 103 | 103 | * In the {} brackets is the pattern that -- | |
| 104 | 104 | * specifies what to extract from the | |
| @@ -107,13 +107,13 @@ | ||
| 107 | 107 | * The string in the field must match the whole pattern -- |
| 108 | 108 | * before brackets, inside brackets, after brackets. |
| 109 | 109 | * When looking at this specific example, we can see that: |
| 110 | 110 | * - A key-value pair with the key `table_location` |
| 111 | - * and the value matching `instances/*` should be added | |
| 111 | + * and the value matching `instances/*` should be added | |
| 112 | 112 | * to the x-goog-request-params routing header. |
| 113 | 113 | * - The value is extracted from the request message's `table_name` field |
| 114 | 114 | * if it matches the full pattern specified: |
| 115 | - * `projects/*/instances/*/tables/*`. | |
| 115 | + * `projects/{@*}instances/{@*}tables/*`. | |
| 116 | 116 | * **NB:** If the `path_template` field is not provided, the key name is |
| 117 | 117 | * equal to the field name, and the whole field should be sent as a value. |
| 118 | 118 | * This makes the pattern for the field and the value functionally equivalent |
| 119 | 119 | * to `**`, and the configuration |
| @@ -129,9 +129,9 @@ | ||
| 129 | 129 | * } |
| 130 | 130 | */ |
| 131 | 131 | public function __construct($data = NULL) |
| 132 | 132 | { |
| 133 | - \Dudlewebs\WPMCS\GPBMetadata\Google\Api\Routing::initOnce(); | |
| 133 | + \Dudlewebs\WPMCS\GCP\GPBMetadata\Google\Api\Routing::initOnce(); | |
| 134 | 134 | parent::__construct($data); |
| 135 | 135 | } |
| 136 | 136 | /** |
| 137 | 137 | * A request field to extract the header key-value pair from. |
| @@ -173,9 +173,9 @@ | ||
| 173 | 173 | * | -- This is the key name in the |
| 174 | 174 | * | | routing header. |
| 175 | 175 | * V | |
| 176 | 176 | * field: "table_name" v |
| 177 | - * path_template: "projects/*/{table_location=instances/*}/tables/*" | |
| 177 | + * path_template: "projects/{@*}{table_location=instances/*}/tables/*" | |
| 178 | 178 | * ^ ^ |
| 179 | 179 | * | | |
| 180 | 180 | * In the {} brackets is the pattern that -- | |
| 181 | 181 | * specifies what to extract from the | |
| @@ -184,13 +184,13 @@ | ||
| 184 | 184 | * The string in the field must match the whole pattern -- |
| 185 | 185 | * before brackets, inside brackets, after brackets. |
| 186 | 186 | * When looking at this specific example, we can see that: |
| 187 | 187 | * - A key-value pair with the key `table_location` |
| 188 | - * and the value matching `instances/*` should be added | |
| 188 | + * and the value matching `instances/*` should be added | |
| 189 | 189 | * to the x-goog-request-params routing header. |
| 190 | 190 | * - The value is extracted from the request message's `table_name` field |
| 191 | 191 | * if it matches the full pattern specified: |
| 192 | - * `projects/*/instances/*/tables/*`. | |
| 192 | + * `projects/{@*}instances/{@*}tables/*`. | |
| 193 | 193 | * **NB:** If the `path_template` field is not provided, the key name is |
| 194 | 194 | * equal to the field name, and the whole field should be sent as a value. |
| 195 | 195 | * This makes the pattern for the field and the value functionally equivalent |
| 196 | 196 | * to `**`, and the configuration |
| @@ -228,9 +228,9 @@ | ||
| 228 | 228 | * | -- This is the key name in the |
| 229 | 229 | * | | routing header. |
| 230 | 230 | * V | |
| 231 | 231 | * field: "table_name" v |
| 232 | - * path_template: "projects/*/{table_location=instances/*}/tables/*" | |
| 232 | + * path_template: "projects/{@*}{table_location=instances/*}/tables/*" | |
| 233 | 233 | * ^ ^ |
| 234 | 234 | * | | |
| 235 | 235 | * In the {} brackets is the pattern that -- | |
| 236 | 236 | * specifies what to extract from the | |
| @@ -239,13 +239,13 @@ | ||
| 239 | 239 | * The string in the field must match the whole pattern -- |
| 240 | 240 | * before brackets, inside brackets, after brackets. |
| 241 | 241 | * When looking at this specific example, we can see that: |
| 242 | 242 | * - A key-value pair with the key `table_location` |
| 243 | - * and the value matching `instances/*` should be added | |
| 243 | + * and the value matching `instances/*` should be added | |
| 244 | 244 | * to the x-goog-request-params routing header. |
| 245 | 245 | * - The value is extracted from the request message's `table_name` field |
| 246 | 246 | * if it matches the full pattern specified: |
| 247 | - * `projects/*/instances/*/tables/*`. | |
| 247 | + * `projects/{@*}instances/{@*}tables/*`. | |
| 248 | 248 | * **NB:** If the `path_template` field is not provided, the key name is |
| 249 | 249 | * equal to the field name, and the whole field should be sent as a value. |
| 250 | 250 | * This makes the pattern for the field and the value functionally equivalent |
| 251 | 251 | * to `**`, and the configuration |