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:
Complex classes like LoggerConfigurationManager often do a lot of different things. To break such a class down, we need to identify a cohesive component within that class. A common approach to find such a component is to look for fields/methods that share the same prefixes, or suffixes. You can also have a look at the cohesion graph to spot any un-connected, or weakly-connected components.
Once you have determined the fields that belong together, you can apply the Extract Class refactoring. If the component makes sense as a sub-class, Extract Subclass is also a candidate, and is often faster.
While breaking up the class, it is a good idea to analyze how other classes use LoggerConfigurationManager, and based on these observations, apply Extract Interface, too.
1 | <?php |
||
15 | class LoggerConfigurationManager |
||
16 | { |
||
17 | /** |
||
18 | * @var Container ログ設定コンテナ |
||
19 | */ |
||
20 | private $logContainer; |
||
21 | |||
22 | /** |
||
23 | * @var Container IOコンテナ |
||
24 | */ |
||
25 | private $ioContainer; |
||
26 | |||
27 | /** |
||
28 | * @var array<string> ログ設定情報 |
||
29 | */ |
||
30 | private $configMap; |
||
31 | |||
32 | /** |
||
33 | * Constructor |
||
34 | * @param mixed $config ログ設定 |
||
35 | * @throws LoggerException |
||
36 | */ |
||
37 | public function __construct($config) |
||
63 | |||
64 | /** |
||
65 | * 設定を読み込む |
||
66 | * @throws LoggerException |
||
67 | */ |
||
68 | public function load() |
||
77 | |||
78 | /** |
||
79 | * ログ設定を返却する |
||
80 | * @return Container ログ設定 |
||
81 | */ |
||
82 | public function getConfig() |
||
86 | |||
87 | /** |
||
88 | * ログレベルを読み込む |
||
89 | * @throws LoggerException |
||
90 | */ |
||
91 | private function loadLogLevel() |
||
102 | |||
103 | /** |
||
104 | * ログ保存先パスを読み込む |
||
105 | * @throws LoggerException |
||
106 | */ |
||
107 | private function loadLogFilePath() |
||
121 | |||
122 | /** |
||
123 | * ログローテートサイクルを読み込む |
||
124 | * @throws LoggerException |
||
125 | */ |
||
126 | private function loadRotateCycle() |
||
134 | |||
135 | /** |
||
136 | * ログローテートサイズを読み込む |
||
137 | * @throws LoggerException |
||
138 | */ |
||
139 | private function loadRotateSize() |
||
152 | |||
153 | /** |
||
154 | * アプリケーション名を読み込む |
||
155 | */ |
||
156 | private function loadApplicationName() |
||
164 | |||
165 | /** |
||
166 | * ロガーフォーマットを読み込む |
||
167 | */ |
||
168 | private function loadFormat() |
||
178 | |||
179 | /** |
||
180 | * ログローテートサイクルを時間に変換 |
||
181 | * @param string ローテートサイクル |
||
182 | * @return int ローテート時間 |
||
183 | * @throws LoggerException |
||
184 | */ |
||
185 | private function cycle2value($cycle) |
||
210 | |||
211 | /** |
||
212 | * ログレベルを数値に変換 |
||
213 | * ログレベルはWebStream独自、PSR-3両方対応 |
||
214 | * @param string ログレベル文字列 |
||
215 | * @throws LoggerException |
||
216 | * @return int ログレベル数値 |
||
217 | */ |
||
218 | View Code Duplication | private function toLogLevelValue(string $level) |
|
244 | } |
||
245 |
Since your code implements the magic setter
_set
, this function will be called for any write access on an undefined variable. You can add the@property
annotation to your class or interface to document the existence of this variable.Since the property has write access only, you can use the @property-write annotation instead.
Of course, you may also just have mistyped another name, in which case you should fix the error.
See also the PhpDoc documentation for @property.