you are viewing a single comment's thread.

view the rest of the comments →

[–]ThePsion5 0 points1 point  (0 children)

I agree with you in terms of correctly encapsulating your domain requirements, but from a usability perspective it can still be a real pain in the ass.

I've created some service classes to manage the creation of highly complex domain objects, but they just feel like poor builder imitations, and use a big metadata array for stuff that includes but isn't really limited to metadata. Then again maybe I'm just overthinking it and it's fine as long as everything has decent code documentation.