Timeline for Is "Introduce Parameter Object" actually a good pattern?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2023 at 9:51 | comment | added | Thomas Junk | @Koenigsberg This pattern doesn't hinder you doing not so smart stuff. OTOH: The code smell isn't hidden as such - as it is in the place like before. Taking parameters as a solo indicator for bad code seems a bit overinterpreted. The bad code is inside the function and having one parameter doesn't make code looking good per se. | |
| Feb 13, 2023 at 8:36 | comment | added | Koenigsberg | One counterpoint to the "Introduce Object Parameter" pattern: What about potentially hiding code smells behind it? Suppose you have a class which takes a bunch of params. You can wrap those params inside a parameter object, but possibly this class holds too much functionality and should be refactored instead. I am wondering about how this pattern adresses such a scenario | |
| Aug 30, 2016 at 12:01 | history | answered | Thomas Junk | CC BY-SA 3.0 |