Conditions | 1 |
Paths | 1 |
Total Lines | 55 |
Lines | 0 |
Ratio | 0 % |
Changes | 0 |
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:
If many parameters/temporary variables are present:
1 | <?php |
||
15 | public static function dataConvertPositionalToNamedParameters() : iterable |
||
16 | { |
||
17 | return [ |
||
18 | [ |
||
19 | 'SELECT name FROM users WHERE id = ?', |
||
20 | 'SELECT name FROM users WHERE id = :param1', |
||
21 | [1 => ':param1'], |
||
22 | ], |
||
23 | [ |
||
24 | 'SELECT name FROM users WHERE id = ? AND status = ?', |
||
25 | 'SELECT name FROM users WHERE id = :param1 AND status = :param2', |
||
26 | [1 => ':param1', 2 => ':param2'], |
||
27 | ], |
||
28 | [ |
||
29 | "UPDATE users SET name = '???', status = ?", |
||
30 | "UPDATE users SET name = '???', status = :param1", |
||
31 | [1 => ':param1'], |
||
32 | ], |
||
33 | [ |
||
34 | "UPDATE users SET status = ?, name = '???'", |
||
35 | "UPDATE users SET status = :param1, name = '???'", |
||
36 | [1 => ':param1'], |
||
37 | ], |
||
38 | [ |
||
39 | "UPDATE users SET foo = ?, name = '???', status = ?", |
||
40 | "UPDATE users SET foo = :param1, name = '???', status = :param2", |
||
41 | [1 => ':param1', 2 => ':param2'], |
||
42 | ], |
||
43 | [ |
||
44 | 'UPDATE users SET name = "???", status = ?', |
||
45 | 'UPDATE users SET name = "???", status = :param1', |
||
46 | [1 => ':param1'], |
||
47 | ], |
||
48 | [ |
||
49 | 'UPDATE users SET status = ?, name = "???"', |
||
50 | 'UPDATE users SET status = :param1, name = "???"', |
||
51 | [1 => ':param1'], |
||
52 | ], |
||
53 | [ |
||
54 | 'UPDATE users SET foo = ?, name = "???", status = ?', |
||
55 | 'UPDATE users SET foo = :param1, name = "???", status = :param2', |
||
56 | [1 => ':param1', 2 => ':param2'], |
||
57 | ], |
||
58 | [ |
||
59 | 'SELECT * FROM users WHERE id = ? AND name = "" AND status = ?', |
||
60 | 'SELECT * FROM users WHERE id = :param1 AND name = "" AND status = :param2', |
||
61 | [1 => ':param1', 2 => ':param2'], |
||
62 | ], |
||
63 | [ |
||
64 | "SELECT * FROM users WHERE id = ? AND name = '' AND status = ?", |
||
65 | "SELECT * FROM users WHERE id = :param1 AND name = '' AND status = :param2", |
||
66 | [1 => ':param1', 2 => ':param2'], |
||
67 | ], |
||
68 | ]; |
||
69 | } |
||
70 | |||
84 |
This check marks access to variables or properties that have not been declared yet. While PHP has no explicit notion of declaring a variable, accessing it before a value is assigned to it is most likely a bug.