Timeline for How to refactor a myriad of similar classes
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2014 at 11:16 | vote | accept | TobiMcNamobi | ||
| Aug 22, 2014 at 6:01 | audit | Suggested edits | |||
| Aug 22, 2014 at 6:02 | |||||
| Aug 21, 2014 at 12:03 | answer | added | AlfredoCasado | timeline score: 1 | |
| Aug 21, 2014 at 11:23 | answer | added | GlenPeterson | timeline score: 0 | |
| Aug 21, 2014 at 10:48 | answer | added | Kevin Hogg | timeline score: 1 | |
| Aug 20, 2014 at 9:09 | comment | added | TobiMcNamobi | @PieterB Think of a class that has one public method that fetches stuff from a database and puts it into a list. Let's say the Single Responsibility Principle is met. AA isn't even hard to create: The type fetched from the DB becomes a template parameter and the call to the DB is outsourced via the Template Method Pattern. The problem here is that the Ax classes are so many. | |
| Aug 20, 2014 at 8:48 | comment | added | Pieter B | I'm wondering what the differences between your similar classes are? How big/small, maybe give an example. | |
| Aug 20, 2014 at 8:35 | comment | added | ratchet freak | duplicating test code isn't bad, and often needed to test all edge cases | |
| Aug 20, 2014 at 8:24 | history | migrated | from stackoverflow.com (revisions) | ||
| Aug 19, 2014 at 10:21 | answer | added | user146705 | timeline score: 0 | |
| Aug 19, 2014 at 9:56 | history | asked | TobiMcNamobi | CC BY-SA 3.0 |