You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: clients/google-api-services-merchantapi/products_v1/2.0.0/com/google/api/services/merchantapi/products_v1/Merchant.java
+35-35Lines changed: 35 additions & 35 deletions
Original file line number
Diff line number
Diff line change
@@ -980,16 +980,16 @@ public class Products {
980
980
* must result in the `content_language~feed_label~offer_id` structure. This encoding MUST be
981
981
* used if any part of the product identifier (like `offer_id`) contains characters such as
982
982
* `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{product}`
983
-
* segment must be the base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The
984
-
* full resource name for the product would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2.
985
-
* **Plain Format**: The `{product}` segment is the tilde-separated string
986
-
* `content_language~feed_label~offer_id`. This format is suitable only when
987
-
* `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters
988
-
* like `/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to
989
-
* ensure correct parsing, especially those containing special characters. The presence of
990
-
* tilde (`~`) characters in the `{product}` segment is used to differentiate between the two
991
-
* formats. Note: For calls to the v1beta version, the plain format is
992
-
* `channel~content_language~feed_label~offer_id`, for example:
983
+
* segment must be the unpadded base64url encoding of this string, which is
984
+
* `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be
985
+
* `accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment
986
+
* is the tilde-separated string `content_language~feed_label~offer_id`. This format is
987
+
* suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-
988
+
* problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format**
989
+
* for all product IDs to ensure correct parsing, especially those containing special
990
+
* characters. The presence of tilde (`~`) characters in the `{product}` segment is used to
991
+
* differentiate between the two formats. Note: For calls to the v1beta version, the plain
992
+
* format is `channel~content_language~feed_label~offer_id`, for example:
993
993
* `accounts/123/products/online~en~US~sku123`.
994
994
* @return the request
995
995
*/
@@ -1029,16 +1029,16 @@ public class Get extends MerchantRequest<com.google.api.services.merchantapi.pro
1029
1029
* must result in the `content_language~feed_label~offer_id` structure. This encoding MUST be
1030
1030
* used if any part of the product identifier (like `offer_id`) contains characters such as
1031
1031
* `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the `{product}`
1032
-
* segment must be the base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The
1033
-
* full resource name for the product would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2.
1034
-
* **Plain Format**: The `{product}` segment is the tilde-separated string
1035
-
* `content_language~feed_label~offer_id`. This format is suitable only when
1036
-
* `content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters
1037
-
* like `/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to
1038
-
* ensure correct parsing, especially those containing special characters. The presence of
1039
-
* tilde (`~`) characters in the `{product}` segment is used to differentiate between the two
1040
-
* formats. Note: For calls to the v1beta version, the plain format is
1041
-
* `channel~content_language~feed_label~offer_id`, for example:
1032
+
* segment must be the unpadded base64url encoding of this string, which is
1033
+
* `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be
1034
+
* `accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment
1035
+
* is the tilde-separated string `content_language~feed_label~offer_id`. This format is
1036
+
* suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-
1037
+
* problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format**
1038
+
* for all product IDs to ensure correct parsing, especially those containing special
1039
+
* characters. The presence of tilde (`~`) characters in the `{product}` segment is used to
1040
+
* differentiate between the two formats. Note: For calls to the v1beta version, the plain
1041
+
* format is `channel~content_language~feed_label~offer_id`, for example:
1042
1042
* `accounts/123/products/online~en~US~sku123`.
1043
1043
* @since 1.13
1044
1044
*/
@@ -1129,9 +1129,9 @@ public Get setUploadProtocol(java.lang.String uploadProtocol) {
1129
1129
* must result in the `content_language~feed_label~offer_id` structure. This encoding MUST
1130
1130
* be used if any part of the product identifier (like `offer_id`) contains characters such
1131
1131
* as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the
1132
-
* `{product}` segment must be the base64url encoding of this string, which is
1133
-
* `ZW5-VVMtc2t1LzEyMw`. The full resource name for the product would be
1134
-
* `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment
1132
+
* `{product}` segment must be the unpadded base64url encoding of this string, which is
1133
+
* `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be
1134
+
* `accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment
1135
1135
* is the tilde-separated string `content_language~feed_label~offer_id`. This format is
1136
1136
* suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-
1137
1137
* problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format**
@@ -1154,15 +1154,15 @@ public Get setUploadProtocol(java.lang.String uploadProtocol) {
1154
1154
Section 5). The decoded string must result in the `content_language~feed_label~offer_id` structure.
1155
1155
This encoding MUST be used if any part of the product identifier (like `offer_id`) contains
1156
1156
characters such as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the
1157
-
`{product}` segment must be the base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`.
1158
-
The full resource name for the product would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2.
1159
-
**Plain Format**: The `{product}` segment is the tilde-separated string
1160
-
`content_language~feed_label~offer_id`. This format is suitable only when `content_language`,
1161
-
`feed_label`, and `offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We
1162
-
recommend using the **Encoded Format** for all product IDs to ensure correct parsing, especially
1163
-
those containing special characters. The presence of tilde (`~`) characters in the `{product}`
1164
-
segment is used to differentiate between the two formats. Note: For calls to the v1beta version,
1165
-
the plain format is `channel~content_language~feed_label~offer_id`, for example:
1157
+
`{product}` segment must be the unpadded base64url encoding of this string, which is
1158
+
`ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be
1159
+
`accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment is the
1160
+
tilde-separated string `content_language~feed_label~offer_id`. This format is suitable only when
1161
+
`content_language`, `feed_label`, and `offer_id` do not contain URL-problematic characters like
1162
+
`/`, `%`, or `~`. We recommend using the **Encoded Format** for all product IDs to ensure correct
1163
+
parsing, especially those containing special characters. The presence of tilde (`~`) characters in
1164
+
the `{product}` segment is used to differentiate between the two formats. Note: For calls to the
1165
+
v1beta version, the plain format is `channel~content_language~feed_label~offer_id`, for example:
1166
1166
`accounts/123/products/online~en~US~sku123`.
1167
1167
*/
1168
1168
publicjava.lang.StringgetName() {
@@ -1181,9 +1181,9 @@ public java.lang.String getName() {
1181
1181
* must result in the `content_language~feed_label~offer_id` structure. This encoding MUST
1182
1182
* be used if any part of the product identifier (like `offer_id`) contains characters such
1183
1183
* as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`, the
1184
-
* `{product}` segment must be the base64url encoding of this string, which is
1185
-
* `ZW5-VVMtc2t1LzEyMw`. The full resource name for the product would be
1186
-
* `accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment
1184
+
* `{product}` segment must be the unpadded base64url encoding of this string, which is
1185
+
* `ZW5-VVN-c2t1LzEyMw`. The full resource name for the product would be
1186
+
* `accounts/123/products/ZW5-VVN-c2t1LzEyMw`. 2. **Plain Format**: The `{product}` segment
1187
1187
* is the tilde-separated string `content_language~feed_label~offer_id`. This format is
1188
1188
* suitable only when `content_language`, `feed_label`, and `offer_id` do not contain URL-
1189
1189
* problematic characters like `/`, `%`, or `~`. We recommend using the **Encoded Format**
0 commit comments