Lets say we have DTO class with 15 properties. Usually DTOs like these are mapped from other objects. But sometimes some DTOs may use values from multiple objects. In these cases, should we “Map” or “Create” an object?
In our project we currently have these scenarios handled by constructors, in some places by static Create methods (a bit inconsistent). We’re doing some refactoring which includes using new MappingService which handles mappings between types. This service supports mapping from multiple source objects. So the question is: should we move constructors creating object from multiple other objects to MappingService or consider them as construction rather than mapping (in which case we may implement some pattern/solution for construction of objects/separately)?
I guess this is more of a terminology question. How do you draw a line of what is mapping and what is construction?