Any mapping always returns an empty object, without any errors about mapper

[nartc]

@apiannikov Thanks for reporting. What “simple mapping” are you referring to? And is 6.3.8 the last version working for you?

[apiannikov]

@nartc, just any mapping to test. I just updated the packages to @nartc/[email protected] and [email protected], and got the unexpected behavior.

Yes, @nartc/[email protected], [email protected] are last versions that work.

[nartc]

https://codesandbox.io/embed/automapper-demo-latest-42cg8?codemirror=1

This example still seems to work for me. Can you please provide a reproduce?

[apiannikov]

@nartc, I just put some code,
user entity
currentUser dto
custom mapper profile
app module with profile addition
mapping usage

[nartc]

Thanks. I’ll take a look asap

[nartc]

@apiannikov https://github.com/nartc/nestjsx-automapper-bug-149 I cannot reproduce the bug with the provided models + mapping configuration. I'm using [email protected] and @nartc/[email protected] (check package.json)

[apiannikov]

Sorry for wasting your time. I checked imports of AutoMapper, they were all from @nartc/automapper, as described in docs. And it worked till the version 6.3.11. But now I've changed imports to nestjsx-automapper and it works. There was a confusion with what package to use for importing AutoMapper.

[nartc]

@apiannikov I see. That’s weird. Can you show the exact imports you used? maybe a TS3.9 problem since nestjsx-automapper just pass through some imports for ease of importing

[nartc]

@apiannikov I have just tested by changing all imports to @nartc/automapper instead of nestjsx-automapper. I'm pretty confident that you'd had run into a problem with conflicting library version. Let me elaborate

nestjsx-automapper has a hard dependencies on @nartc/automapper which internally, nestjsx-automapper is dependent on specific version of @nartc/automapper. When you install nestjsx-automapper, npm will also install @nartc/automapper for you.

[email protected] (prev version) does not have the latest @nartc/automapper version (6.3.11) just yet (1). If you install both nestjsx-automapper and @nartc/automapper in your project, you might run into version conflict because of reason stated above.

(1): I setup nestjsx-automapper dependencies update via dependabot which might be slow to pick up on latest version of @nartc/automapper at times :) Sorry for the inconvenience.

I am closing this issue. Please open a new one if you still run into issues :)