Completed
Branch master (d86252)
by Laurens
04:22 queued 59s
created

ReportInterface

Size/Duplication

Total Lines 22
Duplicated Lines 0 %

Importance

Changes 5
Bugs 0 Features 1
Metric Value
c 5
b 0
f 1
dl 0
loc 22

4 Methods

Rating   Name   Duplication   Size   Complexity  
setFormat() 0 1 ?
setReturnOnlyCompleteData() 0 1 ?
setReportLanguage() 0 1 ?
getRequest() 0 1 ?
1
<?php
2
namespace Werkspot\BingAdsApiBundle\Api\Report;
3
4
interface ReportInterface
5
{
6
    /**
7
     * @param string $format (See BingAds SDK documentation)
8
     */
9
    public function setFormat($format);
0 ignored issues
show
Documentation introduced by
For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
10
11
    /**
12
     * @param bool $returnOnlyCompleteData
13
    */
14
    public function setReturnOnlyCompleteData($returnOnlyCompleteData);
0 ignored issues
show
Documentation introduced by
For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
15
16
    /**
17
    * @param string $language (See BingAds SDK documentation)
18
    */
19
    public function setReportLanguage($language);
0 ignored issues
show
Documentation introduced by
For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
20
21
    /**
22
     * @return mixed
23
     */
24
    public function getRequest();
25
}
26