Skip to content

Commit 65cc2e4

Browse files
feat(specs): conditions is not required anymore in composition rules (generated)
algolia/api-clients-automation#5853 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Clara Muller <[email protected]>
1 parent 7abc5e9 commit 65cc2e4

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

algoliasearch/src/main/java/com/algolia/model/composition/CompositionRule.java

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ public class CompositionRule implements RulesBatchCompositionAction {
1717
private String objectID;
1818

1919
@JsonProperty("conditions")
20-
private List<Condition> conditions = new ArrayList<>();
20+
private List<Condition> conditions;
2121

2222
@JsonProperty("consequence")
2323
private CompositionRuleConsequence consequence;
@@ -51,12 +51,15 @@ public CompositionRule setConditions(List<Condition> conditions) {
5151
}
5252

5353
public CompositionRule addConditions(Condition conditionsItem) {
54+
if (this.conditions == null) {
55+
this.conditions = new ArrayList<>();
56+
}
5457
this.conditions.add(conditionsItem);
5558
return this;
5659
}
5760

5861
/** Conditions that trigger a composition rule. */
59-
@javax.annotation.Nonnull
62+
@javax.annotation.Nullable
6063
public List<Condition> getConditions() {
6164
return conditions;
6265
}

0 commit comments

Comments
 (0)