| Total Lines | 22 |
| Duplicated Lines | 0 % |
| Changes | 5 | ||
| Bugs | 0 | Features | 1 |
| 1 | <?php |
||
| 4 | interface ReportInterface |
||
| 5 | { |
||
| 6 | /** |
||
| 7 | * @param string $format (See BingAds SDK documentation) |
||
| 8 | */ |
||
| 9 | public function setFormat($format); |
||
| 10 | |||
| 11 | /** |
||
| 12 | * @param bool $returnOnlyCompleteData |
||
| 13 | */ |
||
| 14 | public function setReturnOnlyCompleteData($returnOnlyCompleteData); |
||
| 15 | |||
| 16 | /** |
||
| 17 | * @param string $language (See BingAds SDK documentation) |
||
| 18 | */ |
||
| 19 | public function setReportLanguage($language); |
||
| 20 | |||
| 21 | /** |
||
| 22 | * @return mixed |
||
| 23 | */ |
||
| 24 | public function getRequest(); |
||
| 25 | } |
||
| 26 |
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
@returndoc comment to communicate to implementors of these methods what they are expected to return.