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: Sources/RecombeeClient/Requests/AddCartAddition.swift
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -15,22 +15,22 @@ public struct AddCartAddition: Request {
15
15
publicletitemId:String
16
16
17
17
/// UTC timestamp of the cart addition as ISO8601-1 pattern or UTC epoch time. The default value is the current time.
18
-
publicvartimestamp:Date?=nil
18
+
publicvartimestamp:Date?
19
19
20
20
/// Sets whether the given user/item should be created if not present in the database.
21
21
publicvarcascadeCreate:Bool?=true
22
22
23
23
/// Amount (number) added to cart. The default is 1. For example, if `user-x` adds two `item-y` during a single order (session...), the `amount` should equal 2.
24
-
publicvaramount:Double?=nil
24
+
publicvaramount:Double?
25
25
26
26
/// Price of the added item. If `amount` is greater than 1, the sum of prices of all the items should be given.
27
-
publicvarprice:Double?=nil
27
+
publicvarprice:Double?
28
28
29
29
/// If this cart addition is based on a recommendation request, `recommId` is the id of the clicked recommendation.
30
-
publicvarrecommId:String?=nil
30
+
publicvarrecommId:String?
31
31
32
32
/// A dictionary of additional data for the interaction.
Copy file name to clipboardExpand all lines: Sources/RecombeeClient/Requests/AddDetailView.swift
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -15,22 +15,22 @@ public struct AddDetailView: Request {
15
15
publicletitemId:String
16
16
17
17
/// UTC timestamp of the view as ISO8601-1 pattern or UTC epoch time. The default value is the current time.
18
-
publicvartimestamp:Date?=nil
18
+
publicvartimestamp:Date?
19
19
20
20
/// Duration of the view
21
-
publicvarduration:Int?=nil
21
+
publicvarduration:Int?
22
22
23
23
/// Sets whether the given user/item should be created if not present in the database.
24
24
publicvarcascadeCreate:Bool?=true
25
25
26
26
/// If this detail view is based on a recommendation request, `recommId` is the id of the clicked recommendation.
27
-
publicvarrecommId:String?=nil
27
+
publicvarrecommId:String?
28
28
29
29
/// A dictionary of additional data for the interaction.
30
-
publicvaradditionalData:JSONDictionary?=nil
30
+
publicvaradditionalData:JSONDictionary?
31
31
32
32
/// Indicates whether the item was automatically presented to the user (e.g., in a swiping feed) or explicitly requested by the user (e.g., by clicking on a link). Defaults to `false`.
Copy file name to clipboardExpand all lines: Sources/RecombeeClient/Requests/AddPurchase.swift
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -15,25 +15,25 @@ public struct AddPurchase: Request {
15
15
publicletitemId:String
16
16
17
17
/// UTC timestamp of the purchase as ISO8601-1 pattern or UTC epoch time. The default value is the current time.
18
-
publicvartimestamp:Date?=nil
18
+
publicvartimestamp:Date?
19
19
20
20
/// Sets whether the given user/item should be created if not present in the database.
21
21
publicvarcascadeCreate:Bool?=true
22
22
23
23
/// Amount (number) of purchased items. The default is 1. For example, if `user-x` purchases two `item-y` during a single order (session...), the `amount` should equal 2.
24
-
publicvaramount:Double?=nil
24
+
publicvaramount:Double?
25
25
26
26
/// Price paid by the user for the item. If `amount` is greater than 1, the sum of prices of all the items should be given.
27
-
publicvarprice:Double?=nil
27
+
publicvarprice:Double?
28
28
29
29
/// Your profit from the purchased item. The profit is natural in the e-commerce domain (for example, if `user-x` purchases `item-y` for $100 and the gross margin is 30 %, then the profit is $30) but is also applicable in other domains (for example, at a news company it may be income from a displayed advertisement on article page). If `amount` is greater than 1, the sum of profit of all the items should be given.
30
-
publicvarprofit:Double?=nil
30
+
publicvarprofit:Double?
31
31
32
32
/// If this purchase is based on a recommendation request, `recommId` is the id of the clicked recommendation.
33
-
publicvarrecommId:String?=nil
33
+
publicvarrecommId:String?
34
34
35
35
/// A dictionary of additional data for the interaction.
Copy file name to clipboardExpand all lines: Sources/RecombeeClient/Requests/CompositeRecommendation.swift
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -37,38 +37,38 @@ public struct CompositeRecommendation: Request {
37
37
38
38
/// ID of the item for which the recommendations are to be generated.
39
39
40
-
publicvaritemId:String?=nil
40
+
publicvaritemId:String?
41
41
42
42
/// ID of the user for which the recommendations are to be generated.
43
43
44
-
publicvaruserId:String?=nil
44
+
publicvaruserId:String?
45
45
46
46
/// Logic specifies the particular behavior of the recommendation models. You can pick tailored logic for your domain and use case.
47
47
/// See [this section](https://docs.recombee.com/recommendation_logics) for a list of available logics and other details.
48
48
/// The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
49
49
/// Logic can also be set to a [scenario](https://docs.recombee.com/scenarios) in the [Admin UI](https://admin.recombee.com).
50
50
51
-
publicvarlogic:Logic?=nil
51
+
publicvarlogic:Logic?
52
52
53
53
/// ID of the segment from `contextSegmentationId` for which the recommendations are to be generated.
54
54
55
-
publicvarsegmentId:String?=nil
55
+
publicvarsegmentId:String?
56
56
57
57
/// If the entity for the source recommendation does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows, for example, rotations in the following recommendations for that entity, as the entity will be already known to the system.
58
58
59
59
publicvarcascadeCreate:Bool?=true
60
60
61
61
/// Parameters applied for recommending the *Source* stage. The accepted parameters correspond with the recommendation sub-endpoint used to recommend the *Source*.
/// Parameters applied for recommending the *Result* stage. The accepted parameters correspond with the recommendation sub-endpoint used to recommend the *Result*.
Copy file name to clipboardExpand all lines: Sources/RecombeeClient/Requests/RecommendItemSegmentsToItem.swift
+82-8Lines changed: 82 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -43,34 +43,70 @@ public struct RecommendItemSegmentsToItem: Request {
43
43
/// You can set various settings to the [scenario](https://docs.recombee.com/scenarios) in the [Admin UI](https://admin.recombee.com). You can also see the performance of each scenario in the Admin UI separately, so you can check how well each application performs.
44
44
/// The AI that optimizes models to get the best results may optimize different scenarios separately or even use different models in each of the scenarios.
45
45
46
-
publicvarscenario:String?=nil
46
+
publicvarscenario:String?
47
47
48
48
/// If the user does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows, for example, rotations in the following recommendations for that user, as the user will be already known to the system.
49
49
50
50
publicvarcascadeCreate:Bool?=true
51
51
52
52
/// Boolean-returning [ReQL](https://docs.recombee.com/reql) expression which allows you to filter recommended segments based on the `segmentationId`.
53
53
54
-
publicvarfilter:String?=nil
54
+
publicvarfilter:String?
55
55
56
56
/// Number-returning [ReQL](https://docs.recombee.com/reql) expression which allows you to boost recommendation rate of some segments based on the `segmentationId`.
57
57
58
-
publicvarbooster:String?=nil
58
+
publicvarbooster:String?
59
59
60
60
/// Logic specifies the particular behavior of the recommendation models. You can pick tailored logic for your domain and use case.
61
61
/// See [this section](https://docs.recombee.com/recommendation_logics) for a list of available logics and other details.
62
62
/// The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
63
63
/// Logic can also be set to a [scenario](https://docs.recombee.com/scenarios) in the [Admin UI](https://admin.recombee.com).
64
64
65
-
publicvarlogic:Logic?=nil
65
+
publicvarlogic:Logic?
66
66
67
67
/// Dictionary of custom options.
68
68
69
-
publicvarexpertSettings:JSONDictionary?=nil
69
+
publicvarexpertSettings:JSONDictionary?
70
70
71
71
/// If there is a custom AB-testing running, return the name of the group to which the request belongs.
72
72
73
-
publicvarreturnAbGroup:Bool?=nil
73
+
publicvarreturnAbGroup:Bool?
74
+
75
+
/// A dictionary of [ReQL](https://docs.recombee.com/reql) expressions that will be executed for each recommended Item Segment.
76
+
/// This can be used to compute additional properties of the recommended Item Segments.
77
+
/// The keys are the names of the expressions, and the values are the actual ReQL expressions.
0 commit comments