Completed
Push — master ( fe2892...6427ed )
by Oleg
03:03
created

Experiment::__construct()   D

Complexity

Conditions 23
Paths 23

Size

Total Lines 48
Code Lines 38

Duplication

Lines 16
Ratio 33.33 %

Code Coverage

Tests 40
CRAP Score 23.1798

Importance

Changes 0
Metric Value
cc 23
eloc 38
nc 23
nop 1
dl 16
loc 48
ccs 40
cts 43
cp 0.9302
crap 23.1798
rs 4.874
c 0
b 0
f 0

How to fix   Complexity   

Long Method

Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.

For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.

Commonly applied refactorings include:

1
<?php
2
/**
3
 * @author Oleg Krivtsov <[email protected]>
4
 * @date 05 October 2016
5
 * @copyright (c) 2016, Web Marketing ROI
6
 */
7
namespace WebMarketingROI\OptimizelyPHP\Resource\v2;
8
9
use WebMarketingROI\OptimizelyPHP\Exception;
10
use WebMarketingROI\OptimizelyPHP\Resource\v2\Schedule;
11
use WebMarketingROI\OptimizelyPHP\Resource\v2\Variation;
12
use WebMarketingROI\OptimizelyPHP\Resource\v2\Change;
13
use WebMarketingROI\OptimizelyPHP\Resource\v2\Metric;
14
15
/**
16
 * An Optimizely experiment.
17
 */
18
class Experiment
19
{
20
    /**
21
     * The project the Experiment is in
22
     * @var integer
23
     */
24
    private $projectId;
25
    
26
    /**
27
     * List of IDs of all audiences the Experiment is targeted at
28
     * @var array[integer] 
29
     */
30
    private $audienceIds;
31
    
32
    /**
33
     * The ID for the Campaign that the Experiment is in
34
     * @var integer 
35
     */
36
    private $campaignId;
37
    
38
    /**
39
     * Experiment-level changes that will run before all Variations. Typically 
40
     * this is custom CSS or custom JavaScript.
41
     * @var array[Change] 
42
     */
43
    private $changes;
44
    
45
    /**
46
     * The time the experiment was initially created
47
     * @var string 
48
     */
49
    private $created;
50
    
51
    /**
52
     * The description or hypothesis for an Experiment
53
     * @var string 
54
     */
55
    private $description;
56
    
57
    /**
58
     * Percentage expressed as a number from 0-10000 to hold back from being 
59
     * included in the experiment
60
     * @var integer 
61
     */
62
    private $holdback;
63
    
64
    /**
65
     * Unique string identifier for this experiment within the project.
66
     * @var string
67
     */
68
    private $key;
69
    
70
    /**
71
     * The last time the experiment was modified
72
     * @var string 
73
     */
74
    private $lastModified;
75
    
76
    /**
77
     * An ordered list of metrics to track for the experiment
78
     * @var array[Metric] 
79
     */
80
    private $metrics;
81
    
82
    /**
83
     * Name of the Experiment
84
     * @var string 
85
     */
86
    private $name;
87
    
88
    /**
89
     * The last time the experiment was modified
90
     * @var Schedule 
91
     */
92
    private $schedule;
93
    
94
    /**
95
     * Current state of the experiment. Can be 'active', 'paused' or 'archived'.
96
     * @var string 
97
     */
98
    private $status;
99
    
100
    /**
101
     * A list of Variations that each define an experience to show in the context 
102
     * of the Experiment for the purpose of comparison against each other
103
     * @var array[Variation]
104
     */
105
    private $variations = array();
106
    
107
    /**
108
     * The unique identifier for the Experiment
109
     * @var integer 
110
     */
111
    private $id;
112
    
113
    /**
114
     * Whether or not the Experiment is a classic Experiment
115
     * @var boolean
116
     */
117
    private $isClassic;
118
    
119
    /**
120
     * Indicates whether this is a standalone a/b experiment or an experience within a personalization campaign
121
     * Can be a/b or personalization
122
     * @var string
123
     */
124
    private $type;
125
    
126
    /**
127
     * The audiences that should see this experiment. If the field is null or 
128
     * omitted, the experiment will target everyone. Multiple audiences can be 
129
     * combined with "and" or "or" using the same structure as audience conditions
130
     * @var string 
131
     */
132
    private $audienceConditions;
133
        
134
    /**
135
     * Constructor.
136
     */
137 7
    public function __construct($options = array())
138
    {
139 7
        foreach ($options as $name=>$value) {
140
            switch ($name) {
141 6
                case 'project_id': $this->setProjectId($value); break;
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
142 6
                case 'audience_ids': $this->setAudienceIds($value); break;
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
143 6
                case 'campaign_id': $this->setCampaignId($value); break;
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
144 6 View Code Duplication
                case 'changes': {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Coding Style introduced by
case statements should be defined using a colon.

As per the PSR-2 coding standard, case statements should not be wrapped in curly braces. There is no need for braces, since each case is terminated by the next break.

There is also the option to use a semicolon instead of a colon, this is discouraged because many programmers do not even know it works and the colon is universal between programming languages.

switch ($expr) {
    case "A": { //wrong
        doSomething();
        break;
    }
    case "B"; //wrong
        doSomething();
        break;
    case "C": //right
        doSomething();
        break;
}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
145 6
                    $changes = array();
146 6
                    foreach ($value as $changeInfo) {
147 6
                        $changes[] = new Change($changeInfo);
148 6
                    }
149 6
                    $this->setChanges($changes); 
150 6
                    break;
151
                }
152 6
                case 'created': $this->setCreated($value); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
153 6
                case 'description': $this->setDescription($value); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
154 6
                case 'holdback': $this->setHoldback($value); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
155 6
                case 'key': $this->setKey($value); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
156 6
                case 'last_modified': $this->setLastModified($value); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
157 6
                case 'metrics': {
0 ignored issues
show
Coding Style introduced by
case statements should be defined using a colon.

As per the PSR-2 coding standard, case statements should not be wrapped in curly braces. There is no need for braces, since each case is terminated by the next break.

There is also the option to use a semicolon instead of a colon, this is discouraged because many programmers do not even know it works and the colon is universal between programming languages.

switch ($expr) {
    case "A": { //wrong
        doSomething();
        break;
    }
    case "B"; //wrong
        doSomething();
        break;
    case "C": //right
        doSomething();
        break;
}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
158 6
                    $metrics = array();
159 6
                    foreach ($value as $metricInfo) {
160 6
                        $metrics[] = new Metric($metricInfo);
161 6
                    }
162 6
                    $this->setMetrics($metrics); 
163 6
                    break;    
164
                }
165 6
                case 'name': $this->setName($value); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
166 6
                case 'schedule': $this->setSchedule(new Schedule($value)); break;    
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
167 6
                case 'status': $this->setStatus($value); break;
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
168 6 View Code Duplication
                case 'variations': {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
Coding Style introduced by
case statements should be defined using a colon.

As per the PSR-2 coding standard, case statements should not be wrapped in curly braces. There is no need for braces, since each case is terminated by the next break.

There is also the option to use a semicolon instead of a colon, this is discouraged because many programmers do not even know it works and the colon is universal between programming languages.

switch ($expr) {
    case "A": { //wrong
        doSomething();
        break;
    }
    case "B"; //wrong
        doSomething();
        break;
    case "C": //right
        doSomething();
        break;
}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
169 6
                    $variations = array();
170 6
                    foreach ($value as $variationInfo) {
171 6
                        $variations[] = new Variation($variationInfo);
172 6
                    }
173 6
                    $this->setVariations($variations); 
174 6
                    break;
175
                }
176 5
                case 'id': $this->setId($value); break;
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
177 5
                case 'is_classic': $this->setIsClassic($value); break;                
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
178 1
                case 'type': $this->setType($value); break;
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
179 1
                case 'audience_conditions': $this->setAudienceConditions($value); break;                
0 ignored issues
show
Coding Style introduced by
The case body in a switch statement must start on the line following the statement.

According to the PSR-2, the body of a case statement must start on the line immediately following the case statement.

switch ($expr) {
case "A":
    doSomething(); //right
    break;
case "B":

    doSomethingElse(); //wrong
    break;

}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
Coding Style introduced by
Terminating statement must be on a line by itself

As per the PSR-2 coding standard, the break (or other terminating) statement must be on a line of its own.

switch ($expr) {
     case "A":
         doSomething();
         break; //wrong
     case "B":
         doSomething();
         break; //right
     case "C:":
         doSomething();
         return true; //right
 }

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
180
                default:
181
                    throw new Exception('Unknown option found in the Experiment entity: ' . $name);
182
            }
183 7
        }
184 7
    }
185
    
186
    /**
187
     * Returns this object as array.
188
     */
189 3
    public function toArray()
190
    {
191
        $options = array(
192 3
            'project_id' => $this->getProjectId(),
193 3
            'audience_ids' => $this->getAudienceIds(),
194 3
            'campaign_id' => $this->getCampaignId(),
195 3
            'changes' => array(),
196 3
            'created' => $this->getCreated(),
197 3
            'description' => $this->getDescription(),
198 3
            'holdback' => $this->getHoldback(),
199 3
            'key' => $this->getKey(),
200 3
            'last_modified' => $this->getLastModified(),
201 3
            'metrics' => array(),
202 3
            'name' => $this->getName(),
203 3
            'schedule' => $this->getSchedule()?$this->getSchedule()->toArray():null,
204 3
            'status' => $this->getStatus(),
205 3
            'variations' => array(),
206 3
            'id' => $this->getId(),
207 3
            'is_classic' => $this->getIsClassic(),
208 3
            'type' => $this->getType(),
209 3
            'audience_conditions' => $this->getAudienceConditions(),            
210 3
        );
211
        
212 3
        foreach ($this->getChanges() as $change) {
213 3
            $options['changes'][] = $change->toArray();
214 3
        }
215
        
216 3
        foreach ($this->getMetrics() as $metric) {
217 3
            $options['metrics'][] = $metric->toArray();
218 3
        }
219
        
220 3
        foreach ($this->getVariations() as $variation) {
221 3
            $options['variations'][] = $variation->toArray();
222 3
        }
223
        
224
        // Remove options with empty values
225 3
        $cleanedOptions = array();
226 3
        foreach ($options as $name=>$value) {
227 3
            if ($value!==null)
228 3
                $cleanedOptions[$name] = $value;
229 3
        }
230
        
231 3
        return $cleanedOptions;
232
    }
233
    
234 5
    public function getProjectId()
235
    {
236 5
        return $this->projectId;
237
    }
238
    
239 7
    public function setProjectId($projectId)
240
    {
241 7
        $this->projectId = $projectId;
242 7
    }
243
    
244 4
    public function getAudienceIds()
245
    {
246 4
        return $this->audienceIds;
247
    }
248
    
249 7
    public function setAudienceIds($audienceIds)
250
    {
251 7
        $this->audienceIds = $audienceIds;
252 7
    }
253
    
254 4
    public function getCampaignId()
255
    {
256 4
        return $this->campaignId;
257
    }
258
    
259 7
    public function setCampaignId($campaignId)
260
    {
261 7
        $this->campaignId = $campaignId;
262 7
    }
263
    
264 4
    public function getChanges()
265
    {
266 4
        return $this->changes;
267
    }
268
    
269 7
    public function setChanges($changes)
270
    {
271 7
        $this->changes = $changes;
272 7
    }
273
    
274 4
    public function getCreated()
275
    {
276 4
        return $this->created;
277
    }
278
    
279 5
    public function setCreated($created)
280
    {
281 5
        $this->created = $created;
282 5
    }
283
    
284 4
    public function getDescription()
285
    {
286 4
        return $this->description;
287
    }
288
    
289 7
    public function setDescription($description)
290
    {
291 7
        $this->description = $description;
292 7
    }
293
    
294 4
    public function getHoldback()
295
    {
296 4
        return $this->holdback;
297
    }
298
    
299 7
    public function setHoldback($holdback)
300
    {
301 7
        $this->holdback = $holdback;
302 7
    }
303
    
304 4
    public function getKey()
305
    {
306 4
        return $this->key;
307
    }
308
    
309 7
    public function setKey($key)
310
    {
311 7
        $this->key = $key;
312 7
    }
313
    
314 4
    public function getLastModified()
315
    {
316 4
        return $this->lastModified;
317
    }
318
    
319 5
    public function setLastModified($lastModified)
320
    {
321 5
        $this->lastModified = $lastModified;
322 5
    }
323
    
324 4
    public function getMetrics()
325
    {
326 4
        return $this->metrics;
327
    }
328
    
329 7
    public function setMetrics($metrics)
330
    {
331 7
        $this->metrics = $metrics;
332 7
    }
333
    
334 7
    public function getName()
335
    {
336 7
        return $this->name;
337
    }
338
    
339 7
    public function setName($name)
340
    {
341 7
        $this->name = $name;
342 7
    }
343
    
344 4
    public function getSchedule()
345
    {
346 4
        return $this->schedule;
347
    }
348
    
349 7
    public function setSchedule($schedule)
350
    {
351 7
        $this->schedule = $schedule;
352 7
    }
353
    
354 4
    public function getStatus()
355
    {
356 4
        return $this->status;
357
    }
358
    
359 7
    public function setStatus($status)
360
    {
361 7
        $this->status = $status;
362 7
    }
363
    
364 4
    public function getVariations()
365
    {
366 4
        return $this->variations;
367
    }
368
    
369 7
    public function setVariations($variations)
370
    {
371 7
        $this->variations = $variations;
372 7
    }
373
    
374 4
    public function getId()
375
    {
376 4
        return $this->id;
377
    }
378
    
379 5
    public function setId($id)
380
    {
381 5
        $this->id = $id;
382 5
    }
383
    
384 4
    public function getIsClassic()
385
    {
386 4
        return $this->isClassic;
387
    }
388
    
389 5
    public function setIsClassic($isClassic)
390
    {
391 5
        $this->isClassic = $isClassic;
392 5
    }
393
    
394 3
    public function getType()
395
    {
396 3
        return $this->type;
397
    }
398
    
399 2
    public function setType($type)
400
    {
401 2
        $this->type = $type;
402 2
    }
403
    
404 3
    public function getAudienceConditions()
405
    {
406 3
        return $this->audienceConditions;
407
    }
408
    
409 2
    public function setAudienceConditions($audienceConditions)
410
    {
411 2
        $this->audienceConditions = $audienceConditions;
412 2
    }
413
    
414
    public function getConfig()
415
    {
416
        return $this->config;
0 ignored issues
show
Bug introduced by
The property config does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
417
    }
418
    
419
    public function setConfig($config)
420
    {
421
        $this->config = $config;
422
    }
423
}
424
425