Skip to content

Commit 177cd2f

Browse files
1 parent 49e45ff commit 177cd2f

4 files changed

Lines changed: 78 additions & 76 deletions

src/CloudRetail/GoogleCloudRetailV2ConversationalSearchRequest.php

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -43,12 +43,12 @@ class GoogleCloudRetailV2ConversationalSearchRequest extends \Google\Collection
4343
/**
4444
* Optional. The categories associated with a category page. Must be set for
4545
* category navigation queries to achieve good search quality. The format
46-
* should be the same as UserEvent.page_categories; To represent full path of
47-
* category, use '>' sign to separate different hierarchies. If '>' is part of
48-
* the category name, replace it with other character(s). Category pages
49-
* include special pages such as sales or promotions. For instance, a special
50-
* sale page may have the category hierarchy: "pageCategories" : ["Sales >
51-
* 2017 Black Friday Deals"].
46+
* should be the same as UserEvent.page_categories; To represent the full path
47+
* of category, use the '>' sign, with one space on each side, to separate
48+
* different hierarchies. If '>' is part of the category name, replace it with
49+
* other character(s). Category pages include special pages such as sales or
50+
* promotions. For instance, a special sale page may have the category
51+
* hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
5252
*
5353
* @var string[]
5454
*/
@@ -154,12 +154,12 @@ public function getConversationalFilteringSpec()
154154
/**
155155
* Optional. The categories associated with a category page. Must be set for
156156
* category navigation queries to achieve good search quality. The format
157-
* should be the same as UserEvent.page_categories; To represent full path of
158-
* category, use '>' sign to separate different hierarchies. If '>' is part of
159-
* the category name, replace it with other character(s). Category pages
160-
* include special pages such as sales or promotions. For instance, a special
161-
* sale page may have the category hierarchy: "pageCategories" : ["Sales >
162-
* 2017 Black Friday Deals"].
157+
* should be the same as UserEvent.page_categories; To represent the full path
158+
* of category, use the '>' sign, with one space on each side, to separate
159+
* different hierarchies. If '>' is part of the category name, replace it with
160+
* other character(s). Category pages include special pages such as sales or
161+
* promotions. For instance, a special sale page may have the category
162+
* hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
163163
*
164164
* @param string[] $pageCategories
165165
*/

src/CloudRetail/GoogleCloudRetailV2Product.php

Lines changed: 32 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -108,21 +108,22 @@ class GoogleCloudRetailV2Product extends \Google\Collection
108108
*/
109109
public $brands;
110110
/**
111-
* Product categories. This field is repeated for supporting one product
112-
* belonging to several parallel categories. Strongly recommended using the
113-
* full path for better search / recommendation quality. To represent full
114-
* path of category, use '>' sign to separate different hierarchies. If '>' is
115-
* part of the category name, replace it with other character(s). For example,
116-
* if a shoes product belongs to both ["Shoes & Accessories" -> "Shoes"] and
117-
* ["Sports & Fitness" -> "Athletic Clothing" -> "Shoes"], it could be
118-
* represented as: "categories": [ "Shoes & Accessories > Shoes", "Sports &
119-
* Fitness > Athletic Clothing > Shoes" ] Must be set for Type.PRIMARY Product
120-
* otherwise an INVALID_ARGUMENT error is returned. At most 250 values are
121-
* allowed per Product unless overridden through the Google Cloud console.
122-
* Empty values are not allowed. Each value must be a UTF-8 encoded string
123-
* with a length limit of 5,000 characters. Otherwise, an INVALID_ARGUMENT
124-
* error is returned. Corresponding properties: Google Merchant Center
125-
* property google_product_category. Schema.org property [Product.category]
111+
* Optional. Product categories. This field is repeated for supporting one
112+
* product belonging to several parallel categories. Strongly recommended
113+
* using the full path for better search / recommendation quality. To
114+
* represent the full path of category, use the '>' sign, with one space on
115+
* each side, to separate different hierarchies. If '>' is part of the
116+
* category name, replace it with other character(s). For example, if a shoes
117+
* product belongs to both ["Shoes & Accessories" -> "Shoes"] and ["Sports &
118+
* Fitness" -> "Athletic Clothing" -> "Shoes"], it could be represented as:
119+
* "categories": [ "Shoes & Accessories > Shoes", "Sports & Fitness > Athletic
120+
* Clothing > Shoes" ] Must be set for Type.PRIMARY Product otherwise an
121+
* INVALID_ARGUMENT error is returned. At most 250 values are allowed per
122+
* Product unless overridden through the Google Cloud console. Empty values
123+
* are not allowed. Each value must be a UTF-8 encoded string with a length
124+
* limit of 5,000 characters. Otherwise, an INVALID_ARGUMENT error is
125+
* returned. Corresponding properties: Google Merchant Center property
126+
* google_product_category. Schema.org property [Product.category]
126127
* (https://schema.org/category). [mc_google_product_category]:
127128
* https://support.google.com/merchants/answer/6324436
128129
*
@@ -520,21 +521,22 @@ public function getBrands()
520521
return $this->brands;
521522
}
522523
/**
523-
* Product categories. This field is repeated for supporting one product
524-
* belonging to several parallel categories. Strongly recommended using the
525-
* full path for better search / recommendation quality. To represent full
526-
* path of category, use '>' sign to separate different hierarchies. If '>' is
527-
* part of the category name, replace it with other character(s). For example,
528-
* if a shoes product belongs to both ["Shoes & Accessories" -> "Shoes"] and
529-
* ["Sports & Fitness" -> "Athletic Clothing" -> "Shoes"], it could be
530-
* represented as: "categories": [ "Shoes & Accessories > Shoes", "Sports &
531-
* Fitness > Athletic Clothing > Shoes" ] Must be set for Type.PRIMARY Product
532-
* otherwise an INVALID_ARGUMENT error is returned. At most 250 values are
533-
* allowed per Product unless overridden through the Google Cloud console.
534-
* Empty values are not allowed. Each value must be a UTF-8 encoded string
535-
* with a length limit of 5,000 characters. Otherwise, an INVALID_ARGUMENT
536-
* error is returned. Corresponding properties: Google Merchant Center
537-
* property google_product_category. Schema.org property [Product.category]
524+
* Optional. Product categories. This field is repeated for supporting one
525+
* product belonging to several parallel categories. Strongly recommended
526+
* using the full path for better search / recommendation quality. To
527+
* represent the full path of category, use the '>' sign, with one space on
528+
* each side, to separate different hierarchies. If '>' is part of the
529+
* category name, replace it with other character(s). For example, if a shoes
530+
* product belongs to both ["Shoes & Accessories" -> "Shoes"] and ["Sports &
531+
* Fitness" -> "Athletic Clothing" -> "Shoes"], it could be represented as:
532+
* "categories": [ "Shoes & Accessories > Shoes", "Sports & Fitness > Athletic
533+
* Clothing > Shoes" ] Must be set for Type.PRIMARY Product otherwise an
534+
* INVALID_ARGUMENT error is returned. At most 250 values are allowed per
535+
* Product unless overridden through the Google Cloud console. Empty values
536+
* are not allowed. Each value must be a UTF-8 encoded string with a length
537+
* limit of 5,000 characters. Otherwise, an INVALID_ARGUMENT error is
538+
* returned. Corresponding properties: Google Merchant Center property
539+
* google_product_category. Schema.org property [Product.category]
538540
* (https://schema.org/category). [mc_google_product_category]:
539541
* https://support.google.com/merchants/answer/6324436
540542
*

src/CloudRetail/GoogleCloudRetailV2SearchRequest.php

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -137,14 +137,14 @@ class GoogleCloudRetailV2SearchRequest extends \Google\Collection
137137
*/
138138
public $orderBy;
139139
/**
140-
* The categories associated with a category page. Must be set for category
141-
* navigation queries to achieve good search quality. The format should be the
142-
* same as UserEvent.page_categories; To represent full path of category, use
143-
* '>' sign to separate different hierarchies. If '>' is part of the category
144-
* name, replace it with other character(s). Category pages include special
145-
* pages such as sales or promotions. For instance, a special sale page may
146-
* have the category hierarchy: "pageCategories" : ["Sales > 2017 Black Friday
147-
* Deals"].
140+
* Optional. The categories associated with a category page. Must be set for
141+
* category navigation queries to achieve good search quality. The format
142+
* should be the same as UserEvent.page_categories; To represent the full path
143+
* of category, use '>' sign, with one space on each side, to separate
144+
* different hierarchies. If '>' is part of the category name, replace it with
145+
* other character(s). Category pages include special pages such as sales or
146+
* promotions. For instance, a special sale page may have the category
147+
* hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
148148
*
149149
* @var string[]
150150
*/
@@ -506,14 +506,14 @@ public function getOrderBy()
506506
return $this->orderBy;
507507
}
508508
/**
509-
* The categories associated with a category page. Must be set for category
510-
* navigation queries to achieve good search quality. The format should be the
511-
* same as UserEvent.page_categories; To represent full path of category, use
512-
* '>' sign to separate different hierarchies. If '>' is part of the category
513-
* name, replace it with other character(s). Category pages include special
514-
* pages such as sales or promotions. For instance, a special sale page may
515-
* have the category hierarchy: "pageCategories" : ["Sales > 2017 Black Friday
516-
* Deals"].
509+
* Optional. The categories associated with a category page. Must be set for
510+
* category navigation queries to achieve good search quality. The format
511+
* should be the same as UserEvent.page_categories; To represent the full path
512+
* of category, use '>' sign, with one space on each side, to separate
513+
* different hierarchies. If '>' is part of the category name, replace it with
514+
* other character(s). Category pages include special pages such as sales or
515+
* promotions. For instance, a special sale page may have the category
516+
* hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
517517
*
518518
* @param string[] $pageCategories
519519
*/

src/CloudRetail/GoogleCloudRetailV2UserEvent.php

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -120,15 +120,15 @@ class GoogleCloudRetailV2UserEvent extends \Google\Collection
120120
*/
121121
public $orderBy;
122122
/**
123-
* The categories associated with a category page. To represent full path of
124-
* category, use '>' sign to separate different hierarchies. If '>' is part of
125-
* the category name, replace it with other character(s). Category pages
126-
* include special pages such as sales or promotions. For instance, a special
127-
* sale page may have the category hierarchy: "pageCategories" : ["Sales >
128-
* 2017 Black Friday Deals"]. Required for `category-page-view` events. At
129-
* least one of search_query or page_categories is required for `search`
130-
* events. Other event types should not set this field. Otherwise, an
131-
* INVALID_ARGUMENT error is returned.
123+
* Optional. The categories associated with a category page. To represent the
124+
* full path of category, use the '>' sign, with one space on each side, to
125+
* separate different hierarchies. If '>' is part of the category name,
126+
* replace it with other character(s). Category pages include special pages
127+
* such as sales or promotions. For instance, a special sale page may have the
128+
* category hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
129+
* Required for `category-page-view` events. At least one of search_query or
130+
* page_categories is required for `search` events. Other event types should
131+
* not set this field. Otherwise, an INVALID_ARGUMENT error is returned.
132132
*
133133
* @var string[]
134134
*/
@@ -444,15 +444,15 @@ public function getOrderBy()
444444
return $this->orderBy;
445445
}
446446
/**
447-
* The categories associated with a category page. To represent full path of
448-
* category, use '>' sign to separate different hierarchies. If '>' is part of
449-
* the category name, replace it with other character(s). Category pages
450-
* include special pages such as sales or promotions. For instance, a special
451-
* sale page may have the category hierarchy: "pageCategories" : ["Sales >
452-
* 2017 Black Friday Deals"]. Required for `category-page-view` events. At
453-
* least one of search_query or page_categories is required for `search`
454-
* events. Other event types should not set this field. Otherwise, an
455-
* INVALID_ARGUMENT error is returned.
447+
* Optional. The categories associated with a category page. To represent the
448+
* full path of category, use the '>' sign, with one space on each side, to
449+
* separate different hierarchies. If '>' is part of the category name,
450+
* replace it with other character(s). Category pages include special pages
451+
* such as sales or promotions. For instance, a special sale page may have the
452+
* category hierarchy: "pageCategories" : ["Sales > 2017 Black Friday Deals"].
453+
* Required for `category-page-view` events. At least one of search_query or
454+
* page_categories is required for `search` events. Other event types should
455+
* not set this field. Otherwise, an INVALID_ARGUMENT error is returned.
456456
*
457457
* @param string[] $pageCategories
458458
*/

0 commit comments

Comments
 (0)