Complex classes like StyleHelper 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 StyleHelper, and based on these observations, apply Extract Interface, too.
1 | <?php |
||
13 | class StyleHelper |
||
14 | { |
||
15 | /** Paths of XML files relative to the XLSX file root */ |
||
16 | const STYLES_XML_FILE_PATH = 'xl/styles.xml'; |
||
17 | |||
18 | /** Nodes used to find relevant information in the styles XML file */ |
||
19 | const XML_NODE_NUM_FMTS = 'numFmts'; |
||
20 | const XML_NODE_NUM_FMT = 'numFmt'; |
||
21 | const XML_NODE_CELL_XFS = 'cellXfs'; |
||
22 | const XML_NODE_XF = 'xf'; |
||
23 | |||
24 | /** Attributes used to find relevant information in the styles XML file */ |
||
25 | const XML_ATTRIBUTE_NUM_FMT_ID = 'numFmtId'; |
||
26 | const XML_ATTRIBUTE_FORMAT_CODE = 'formatCode'; |
||
27 | const XML_ATTRIBUTE_APPLY_NUMBER_FORMAT = 'applyNumberFormat'; |
||
28 | |||
29 | /** By convention, default style ID is 0 */ |
||
30 | const DEFAULT_STYLE_ID = 0; |
||
31 | |||
32 | const NUMBER_FORMAT_GENERAL = 'General'; |
||
33 | |||
34 | /** |
||
35 | * @see https://msdn.microsoft.com/en-us/library/ff529597(v=office.12).aspx |
||
36 | * @var array Mapping between built-in numFmtId and the associated format - for dates only |
||
37 | */ |
||
38 | protected static $builtinNumFmtIdToNumFormatMapping = [ |
||
39 | 14 => 'm/d/yyyy', // @NOTE: ECMA spec is 'mm-dd-yy' |
||
40 | 15 => 'd-mmm-yy', |
||
41 | 16 => 'd-mmm', |
||
42 | 17 => 'mmm-yy', |
||
43 | 18 => 'h:mm AM/PM', |
||
44 | 19 => 'h:mm:ss AM/PM', |
||
45 | 20 => 'h:mm', |
||
46 | 21 => 'h:mm:ss', |
||
47 | 22 => 'm/d/yyyy h:mm', // @NOTE: ECMA spec is 'm/d/yy h:mm', |
||
48 | 45 => 'mm:ss', |
||
49 | 46 => '[h]:mm:ss', |
||
50 | 47 => 'mm:ss.0', // @NOTE: ECMA spec is 'mmss.0', |
||
51 | ]; |
||
52 | |||
53 | /** @var string Path of the XLSX file being read */ |
||
54 | protected $filePath; |
||
55 | |||
56 | /** @var array Array containing the IDs of built-in number formats indicating a date */ |
||
57 | protected $builtinNumFmtIdIndicatingDates; |
||
58 | |||
59 | /** @var array Array containing a mapping NUM_FMT_ID => FORMAT_CODE */ |
||
60 | protected $customNumberFormats; |
||
61 | |||
62 | /** @var array Array containing a mapping STYLE_ID => [STYLE_ATTRIBUTES] */ |
||
63 | protected $stylesAttributes; |
||
64 | |||
65 | /** @var array Cache containing a mapping NUM_FMT_ID => IS_DATE_FORMAT. Used to avoid lots of recalculations */ |
||
66 | protected $numFmtIdToIsDateFormatCache = []; |
||
67 | |||
68 | /** |
||
69 | * @param string $filePath Path of the XLSX file being read |
||
70 | */ |
||
71 | 192 | public function __construct($filePath) |
|
76 | |||
77 | /** |
||
78 | * Returns whether the style with the given ID should consider |
||
79 | * numeric values as timestamps and format the cell as a date. |
||
80 | * |
||
81 | * @param int $styleId Zero-based style ID |
||
82 | * @return bool Whether the cell with the given cell should display a date instead of a numeric value |
||
83 | */ |
||
84 | 129 | public function shouldFormatNumericValueAsDate($styleId) |
|
99 | |||
100 | /** |
||
101 | * Reads the styles.xml file and extract the relevant information from the file. |
||
102 | * |
||
103 | * @return void |
||
104 | */ |
||
105 | 30 | protected function extractRelevantInfo() |
|
125 | |||
126 | /** |
||
127 | * Extracts number formats from the "numFmt" nodes. |
||
128 | * For simplicity, the styles attributes are kept in memory. This is possible thanks |
||
129 | * to the reuse of formats. So 1 million cells should not use 1 million formats. |
||
130 | * |
||
131 | * @param \Box\Spout\Reader\Wrapper\XMLReader $xmlReader XML Reader positioned on the "numFmts" node |
||
132 | * @return void |
||
133 | */ |
||
134 | 21 | protected function extractNumberFormats($xmlReader) |
|
147 | |||
148 | /** |
||
149 | * Extracts style attributes from the "xf" nodes, inside the "cellXfs" section. |
||
150 | * For simplicity, the styles attributes are kept in memory. This is possible thanks |
||
151 | * to the reuse of styles. So 1 million cells should not use 1 million styles. |
||
152 | * |
||
153 | * @param \Box\Spout\Reader\Wrapper\XMLReader $xmlReader XML Reader positioned on the "cellXfs" node |
||
154 | * @return void |
||
155 | */ |
||
156 | 30 | protected function extractStyleAttributes($xmlReader) |
|
176 | |||
177 | /** |
||
178 | * @return array The custom number formats |
||
179 | */ |
||
180 | 15 | protected function getCustomNumberFormats() |
|
181 | { |
||
182 | 15 | if (!isset($this->customNumberFormats)) { |
|
183 | $this->extractRelevantInfo(); |
||
184 | } |
||
185 | |||
186 | 15 | return $this->customNumberFormats; |
|
187 | } |
||
188 | |||
189 | /** |
||
190 | * @return array The styles attributes |
||
191 | */ |
||
192 | 30 | protected function getStylesAttributes() |
|
200 | |||
201 | /** |
||
202 | * @param array $styleAttributes Array containing the style attributes (2 keys: "applyNumberFormat" and "numFmtId") |
||
203 | * @return bool Whether the style with the given attributes indicates that the number is a date |
||
204 | */ |
||
205 | 111 | protected function doesStyleIndicateDate($styleAttributes) |
|
221 | |||
222 | /** |
||
223 | * Returns whether the number format ID indicates that the number is a date. |
||
224 | * The result is cached to avoid recomputing the same thing over and over, as |
||
225 | * "numFmtId" attributes can be shared between multiple styles. |
||
226 | * |
||
227 | * @param int $numFmtId |
||
228 | * @return bool Whether the number format ID indicates that the number is a date |
||
229 | */ |
||
230 | 105 | protected function doesNumFmtIdIndicateDate($numFmtId) |
|
243 | |||
244 | /** |
||
245 | * @param int $numFmtId |
||
246 | * @return string|null The custom number format or NULL if none defined for the given numFmtId |
||
247 | */ |
||
248 | 105 | protected function getFormatCodeForNumFmtId($numFmtId) |
|
255 | |||
256 | /** |
||
257 | * @param int $numFmtId |
||
258 | * @return bool Whether the number format ID indicates that the number is a date |
||
259 | */ |
||
260 | 105 | protected function isNumFmtIdBuiltInDateFormat($numFmtId) |
|
264 | |||
265 | /** |
||
266 | * @param string|null $formatCode |
||
267 | * @return bool Whether the given format code indicates that the number is a date |
||
268 | */ |
||
269 | 99 | protected function isFormatCodeCustomDateFormat($formatCode) |
|
278 | |||
279 | /** |
||
280 | * @param string $formatCode |
||
281 | * @return bool Whether the given format code matches a date format pattern |
||
282 | */ |
||
283 | 81 | protected function isFormatCodeMatchingDateFormatPattern($formatCode) |
|
307 | |||
308 | /** |
||
309 | * Returns the format as defined in "styles.xml" of the given style. |
||
310 | * NOTE: It is assumed that the style DOES have a number format associated to it. |
||
311 | * |
||
312 | * @param int $styleId Zero-based style ID |
||
313 | * @return string The number format code associated with the given style |
||
314 | */ |
||
315 | 6 | public function getNumberFormatCode($styleId) |
|
330 | } |
||
331 |