Timeline for A generic helper class, a project specific class, and the rest of project
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2016 at 8:05 | vote | accept | Sharky | ||
| Feb 1, 2016 at 15:12 | comment | added | Andy | I am pretty sure you can mock the object even without using an interface. The basic usage of dependency injections fulfills the contract. | |
| Feb 1, 2016 at 14:31 | comment | added | Sharky | ..worths it. Well whatever, it starts feeling like paralysis by analysis. i should move on. Thanks again Doc! | |
| Feb 1, 2016 at 14:31 | comment | added | Sharky | Thank you for your answer. Creating that general helper twice (once in project and once internally in the project-specific-class) will surely make things less complex, and would lead to just forget about it. But i am willing to add a bit "complexity" should i say? by just creating the general helper one time and then make sure i am passing it to the project specific class. (Since wherever i use the project specific class there is always the general helper also already present). So i think i won't "keep things as simple as possible" for the sake of micro(?)optimization - not sure if actually | |
| Feb 1, 2016 at 14:15 | history | answered | Doc Brown | CC BY-SA 3.0 |