Timeline for For more than one parameter, when NOT to introduce parameter object?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2023 at 5:59 | comment | added | greenoldman | I use parameter objects basically in three cases: I have a lot parameters to start with, I keep adding parameters or/and I would like to resolve target method based on type of parameter (in the last case not only I have parameter objects but also unique ones). | |
| Oct 4, 2023 at 19:44 | comment | added | Doc Brown | "should be refactored as" - em, no. Those question (as well as most other serious resources about that topic ) tell you one can refactor the first form into the second, not that you should. The top answer of your second reference speaks of a recommendation to introduce a parameter object for related parameters. | |
| Oct 4, 2023 at 13:07 | answer | added | Robert Bräutigam | timeline score: 3 | |
| Oct 4, 2023 at 7:01 | answer | added | DavidT | timeline score: 8 | |
| Oct 4, 2023 at 6:44 | history | asked | wcminipgasker2023 | CC BY-SA 4.0 |