Mapping with both null and undefined

[kami4ka]

This mapper is the most powerful and maintained that I've seen and I appreciate all the job done.

I have a question regarding this mapper.
My app architecture consists of 3 layers: API, domain and database.
While using PATCH I'd like to be able to differentiate null and undefined on the database layer entities.

So my question: is it possible to keep undefined properties as undefined and null properties as null while mapping?

[nartc]

@kami4ka Sorry for getting back to you this late. Thanks for the kind words. And thanks for reporting the issue. As of the moment, it's not possible unfortunately. It's either null OR undefined at this point. However, it's entirely possible to fix. With that said, there's also #208 where I'd love to spend a little more time into rethink how I want defaults in AutoMapper to take shape.

I'll look into this as soon as I am settled with the new job (not an excuse but that's why I've been away, I took on a new offer 😉)

[kami4ka]

@nartc Thanks for the response. Can you please suggest if it's possible somehow to fix the behavior locally?

[nartc]

@kami4ka I'm thinking that it's possible and probably is going to require some work. If you could provide a sample repo then I can jump in and hack at it.

[kami4ka]

@nartc It's really a quite simple example with 3 classes that contain the same fields (as we have a 3 layer app).
We're using @AutoMap() decorator for all the fields and just creating maps with .createMap(Request, Domain) and .createMap(Domain, Entity).reverseMap() calls.

[kami4ka]

Hi, @nartc . Any updates regarding this issue? Can I somehow help/contribute?

[abouroubi]

Would love to see this feature too, I can help if needed

[nartc]

Closing this due to #243 . I won't be adding this to the current @nartc/automapper as stated in the announcement. That said, this will be available in the new version. Sorry for any inconvenience.
cc @kami4ka @abouroubi. Sorry for the long delay and ultimately close the issue without a solution. Please read the announcement for the reasons and future changes. Thanks for understanding.