These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | /** |
||
3 | * SignalService.php |
||
4 | * |
||
5 | * General file information |
||
6 | * |
||
7 | * @category Extension |
||
8 | * @package importr |
||
9 | * @author Tim Spiekerkoetter HDNET GmbH & Co. <[email protected]> |
||
10 | * @version CVS: $Id:08.02.13$ |
||
11 | */ |
||
12 | namespace HDNET\Importr\Service; |
||
13 | |||
14 | /** |
||
15 | * SignalService.php |
||
16 | * |
||
17 | * General class information |
||
18 | * |
||
19 | * @package importr |
||
20 | * @subpackage Service |
||
21 | * @author Tim Spiekerkoetter HDNET GmbH & Co. <[email protected]> |
||
22 | */ |
||
23 | class SignalService |
||
24 | { |
||
25 | /** |
||
26 | * @deprecated |
||
27 | */ |
||
28 | public function truncateTable() |
||
29 | { |
||
30 | \HDNET\Importr\Feature\TruncateTable::enable('preParseConfiguration'); |
||
0 ignored issues
–
show
|
|||
31 | } |
||
32 | |||
33 | /** |
||
34 | * @deprecated |
||
35 | */ |
||
36 | public function renameFile() |
||
37 | { |
||
38 | \HDNET\Importr\Feature\RenameFile::enable('afterImport'); |
||
0 ignored issues
–
show
The call to
RenameFile::enable() has too many arguments starting with 'afterImport' .
This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue. If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. In this case you can add the
Loading history...
|
|||
39 | } |
||
40 | } |
||
41 |
This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.
In this case you can add the
@ignore
PhpDoc annotation to the duplicate definition and it will be ignored.