Duplicate code is one of the most pungent code smells. A rule that is often used is to re-structure code once it is duplicated in three or more places.
Common duplication problems, and corresponding solutions are:
1 | <?php |
||
5 | View Code Duplication | class MakeSeederCommand extends MakeCommand |
|
|
|||
6 | { |
||
7 | /** |
||
8 | * The name and signature of the console command. |
||
9 | * |
||
10 | * @var string |
||
11 | */ |
||
12 | protected $signature = 'make:module:seeder |
||
13 | {slug : The slug of the module.} |
||
14 | {name : The name of the seeder class.}'; |
||
15 | |||
16 | /** |
||
17 | * The console command description. |
||
18 | * |
||
19 | * @var string |
||
20 | */ |
||
21 | protected $description = 'Create a new module seeder class'; |
||
22 | |||
23 | /** |
||
24 | * String to store the command type. |
||
25 | * |
||
26 | * @var string |
||
27 | */ |
||
28 | protected $type = 'Seeder'; |
||
29 | |||
30 | /** |
||
31 | * Module folders to be created. |
||
32 | * |
||
33 | * @var array |
||
34 | */ |
||
35 | protected $listFolders = [ |
||
36 | 'Database/Seeds/' |
||
37 | ]; |
||
38 | |||
39 | /** |
||
40 | * Module files to be created. |
||
41 | * |
||
42 | * @var array |
||
43 | */ |
||
44 | protected $listFiles = [ |
||
45 | '{{filename}}.php' |
||
46 | ]; |
||
47 | |||
48 | /** |
||
49 | * Module stubs used to populate defined files. |
||
50 | * |
||
51 | * @var array |
||
52 | */ |
||
53 | protected $listStubs = [ |
||
54 | 'default' => [ |
||
55 | 'seeder_plus.stub' |
||
56 | ] |
||
57 | ]; |
||
58 | |||
59 | /** |
||
60 | * Resolve Container after getting file path |
||
61 | * |
||
62 | * @param string $FilePath |
||
63 | * @return Array |
||
64 | */ |
||
65 | protected function resolveByPath($filePath) |
||
71 | |||
72 | /** |
||
73 | * Replace placeholder text with correct values. |
||
74 | * |
||
75 | * @return string |
||
76 | */ |
||
77 | protected function formatContent($content) |
||
93 | } |
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.