Auto generate asserts on Mappings about modelmapper HOT 3 CLOSED

Right now ModelMapper's validation is intended to verify that the structure of some class maps to the structure of another class, via the validate() method. It is possible that the source object you use might have some null values which obviously would result in null values being set on the destination, but ModelMapper will still copy those null values over as long as the source/destination properties are mapped.

Can you give me a better idea of what you had in mind for asserting things?

from modelmapper.

I was thinking on the lines of code generation for asserts so that the developer knows exactly how things are getting mapped. Also, refactorings like field name changes can be guarded with the tests.

from modelmapper.

I think that code gen for assertions is outside the scope of ModelMapper for now. I would like to support any sort of validation that can be done without code gen, but code gen adds more complexity for users than I'd like.

I would encourage you to take a stab at building and publishing your own extension/library for this though. If you do, let me know when it's completed and I'll link to it on the site :)

from modelmapper.