Version 7 causes compilation issues due to 'unexpected any', is this as intended?

[PieterBoeren]

Hi,

Not sure if this is working as intended or not, but with version 6.* this code worked perfectly (profile):

 mapper
    .createMap(SomeDto, SomeViewModel)
    .forMember(
      (destination) => destination.someValue,
      mapFrom((source) => new Date(source.someOtherValue))
    )

(Basically same as in the documentation)

But in version 7, this all of a sudden gives me compilation errors like:

TS7006: Parameter 'destination' implicitly has an 'any' type.

It's fixable by supplying the correct types (destination: SomeViewModel and source: SomeDto), but is this expected? And if so, it should probably be added to the breaking changes I guess.

[nartc]

Have you changed the type import from automapper/types to automapper/core? It is a breaking change

[nartc]

I should have changed the documentation first before releasing 🤦‍♂️

[micalevisk]

every time I face a major upgrade, I go to releases page to read about the breaking changes :p

[PieterBoeren]

Me as well, just forgot to update my imports (TypeScript should stop emitting other errors if the imports are failing :)).

[nartc]

Updated docs site :D

[nartc]

@micalevisk Release now contains the CHANGELOG information as well.