"Invalid Date" result for Date[] mappings

[roblopz]

Is there an existing issue for this?

• I have searched the existing issues

Describe the issue

It seems there's a bug on the classes plugin when mapping properties of type Date[]. Date[] properties are mapped to 'Invalid Date' instead of the expected array of date objects.

Models/DTOs/VMs

export class Invite {
@AutoMap({ typeFn: () => String })
_id: string;

@AutoMap({ typeFn: () => String })
main: string;

@AutoMap({ typeFn: () => Date })
logins?: Date[];

@AutoMap({ typeFn: () => Date })
sentAt: Date;
}

export class InviteDTO {
@AutoMap({ typeFn: () => String })
_id: string;

@AutoMap({ typeFn: () => String })
main: string;

@AutoMap({ typeFn: () => Date })
logins?: Date[];

@AutoMap({ typeFn: () => Date })
sentAt: Date;
}

Mapping configuration

import { createMapper } from '@automapper/core';
import { classes } from '@automapper/classes';

export const mapper = createMapper({
name: 'appMapper',
pluginInitializer: classes
});

Steps to reproduce

/*
Using above described classes and mapping config...
*/

function inviteFactory() {
const invite = new Invite();
invite._id = 'SomeId';
invite.main = 'SomeString';
invite.sentAt = new Date();
invite.logins = [new Date(), new Date(), new Date()];
return invite;
}

const invite = inviteFactory();
const dto = this.mapper.map(invite, InviteDTO, Invite);

// OK, Date-type is correctly being mapped
expect(dto.sentAt).toBeValidDate();

// FAIL, Date[]-type is being mapped to an invalid date object
expect(dto.logins).toBeAnArray();

// FAIL, dto.logins is NOT an array here as it should be, it's an invalid date object
dto.logins.forEach(date => expect(date).toBeValidDate);

Expected behavior

Date[] properties are correctly mapped.

Screenshots

No response

Minimum reproduction code

No response

Package

• I don't know.
• @automapper/core
• @automapper/classes
• @automapper/nestjs
• @automapper/pojos
• @automapper/sequelize
• @automapper/types
• Other (see below)

Other package and its version

No response

AutoMapper version

6.2.1

Additional context

No response

[micalevisk]

I guess this is due to this limitation: https://automapperts.netlify.app/docs/misc/limitations#date-time

[roblopz]

I guess this is due to this limitation: https://automapperts.netlify.app/docs/misc/limitations#date-time

The thing is, even when providing a custom mapFrom function on the configuration, I'm getting my source object with this 'Invalid Date' value instead of the Date[] value.. any workaround you can think of?

[nartc]

@roblopz I'll take a look tomorrow. Thank you for reporting

[roblopz]

I've created a quite simple PR #398 that I think shouldn't break anything else.

Thanks @nartc, @micalevisk.

[roblopz]

New and corrected PR #399

Thanks!