There is nothing wrong with a view knowing how to display an object - in
fact making it 'agnostic' when there is nothing agnostic about it is an
anti-pattern. If you did find things that were common across more than one
entity its a simple matter of abstracting that out into a base control
later.
Hello,
I have a more ore or less complicated business object, that looks
similar to this:
has some properties (id, pubdate...)
and a list of s
each has a language, a title and a description and a list of
s
each , has a List of s with Title and Description
To edit the objects properties I crea
