Conditions | 11 |
Paths | 24 |
Total Lines | 90 |
Code Lines | 62 |
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 |
||
42 | public function execute() { |
||
43 | if ( !$this->hasOption( 'delete' ) ) { |
||
44 | $this->output( "Use --delete to actually confirm this script\n" ); |
||
45 | return; |
||
46 | } |
||
47 | |||
48 | # Data should come off the master, wrapped in a transaction |
||
49 | $dbw = $this->getDB( DB_MASTER ); |
||
50 | $this->beginTransaction( $dbw, __METHOD__ ); |
||
51 | $repo = RepoGroup::singleton()->getLocalRepo(); |
||
52 | |||
53 | # Get "active" revisions from the filearchive table |
||
54 | $this->output( "Searching for and deleting archived files...\n" ); |
||
55 | $res = $dbw->select( |
||
56 | 'filearchive', |
||
57 | [ 'fa_id', 'fa_storage_group', 'fa_storage_key', 'fa_sha1', 'fa_name' ], |
||
58 | '', |
||
59 | __METHOD__ |
||
60 | ); |
||
61 | |||
62 | $count = 0; |
||
63 | foreach ( $res as $row ) { |
||
64 | $key = $row->fa_storage_key; |
||
65 | if ( !strlen( $key ) ) { |
||
66 | $this->output( "Entry with ID {$row->fa_id} has empty key, skipping\n" ); |
||
67 | continue; |
||
68 | } |
||
69 | |||
70 | /** @var LocalFile $file */ |
||
71 | $file = $repo->newFile( $row->fa_name ); |
||
72 | try { |
||
73 | $file->lock(); |
||
74 | } catch ( LocalFileLockError $e ) { |
||
75 | $this->error( "Could not acquire lock on '{$row->fa_name}', skipping\n" ); |
||
76 | continue; |
||
77 | } |
||
78 | |||
79 | $group = $row->fa_storage_group; |
||
80 | $id = $row->fa_id; |
||
81 | $path = $repo->getZonePath( 'deleted' ) . |
||
82 | '/' . $repo->getDeletedHashPath( $key ) . $key; |
||
83 | if ( isset( $row->fa_sha1 ) ) { |
||
84 | $sha1 = $row->fa_sha1; |
||
85 | } else { |
||
86 | // old row, populate from key |
||
87 | $sha1 = LocalRepo::getHashFromKey( $key ); |
||
88 | } |
||
89 | |||
90 | // Check if the file is used anywhere... |
||
91 | $inuse = $dbw->selectField( |
||
92 | 'oldimage', |
||
93 | '1', |
||
94 | [ |
||
95 | 'oi_sha1' => $sha1, |
||
96 | $dbw->bitAnd( 'oi_deleted', File::DELETED_FILE ) => File::DELETED_FILE |
||
97 | ], |
||
98 | __METHOD__, |
||
99 | [ 'FOR UPDATE' ] |
||
100 | ); |
||
101 | |||
102 | $needForce = true; |
||
103 | if ( !$repo->fileExists( $path ) ) { |
||
104 | $this->output( "Notice - file '$key' not found in group '$group'\n" ); |
||
105 | } elseif ( $inuse ) { |
||
106 | $this->output( "Notice - file '$key' is still in use\n" ); |
||
107 | } elseif ( !$repo->quickPurge( $path ) ) { |
||
108 | $this->output( "Unable to remove file $path, skipping\n" ); |
||
109 | $file->unlock(); |
||
110 | continue; // don't delete even with --force |
||
111 | } else { |
||
112 | $needForce = false; |
||
113 | } |
||
114 | |||
115 | if ( $needForce ) { |
||
116 | if ( $this->hasOption( 'force' ) ) { |
||
117 | $this->output( "Got --force, deleting DB entry\n" ); |
||
118 | } else { |
||
119 | $file->unlock(); |
||
120 | continue; |
||
121 | } |
||
122 | } |
||
123 | |||
124 | $count++; |
||
125 | $dbw->delete( 'filearchive', [ 'fa_id' => $id ], __METHOD__ ); |
||
126 | $file->unlock(); |
||
127 | } |
||
128 | |||
129 | $this->commitTransaction( $dbw, __METHOD__ ); |
||
130 | $this->output( "Done! [$count file(s)]\n" ); |
||
131 | } |
||
132 | } |
||
136 |
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.