DEV Community

Discussion on: Kentico Xperience Design Patterns: Multiple Types Per File

Collapse
 
themarkschmidt profile image
themarkschmidt

Thanks for the detailed reply @seangwright . It "feels" like it breaks so many rules that are in my head (one file, one thing). But it does keep things simpler and still follows (one file, one "concept"). They are all heavily related objects, and typically if one thing changes, then a few of them may change. Which... still follows the rule. It does feel cleaner (not 10 files all over the place, when you make "one change" and have to touch all of them). And, at the end of the day, as soon as something else is using it, you can easily refactor/extract. I'll have to give it a try. Thanks agian.

Thread Thread
 
seangwright profile image
Sean G. Wright

I think you made a perfect TLDR of my post!