Annotations not working with constructor

[lacoonte]

I have two classes:

export default class Timetable {
  @AutoMap({ typeFn: () => Workday })
  workdays: Workday[];
  startDate: Date;
  endDate: Date;
  constructor(workdays: Workday[], startDate: Date, endDate: Date) {
    this.workdays = workdays;
    this.startDate = startDate;
    this.endDate = endDate;
  }
}

and:

export default class Workday {
  @AutoMap({ typeFn: () => Number })
  day: WeekDay;
  @AutoMap()
  startTime: Date;
  @AutoMap()
  endTime: Date;
  constructor(
    day: WeekDay,
    startTime: Date,
    endTime: Date
  ) {
    this.day = day;
    this.startTime = startTime;
    this.endTime = endTime;
  }
}

Unless I remove the constructor in workday, i get the following error over "typeFn" in Timetable:
Type '() => typeof Workday' is not assignable to type '() => Constructible<any>'. Type 'typeof Workday' is not assignable to type 'Constructible<any>'. Types of parameters 'day' and 'args' are incompatible. Type 'unknown' is not assignable to type 'number'.ts(2322) automap.decorator.d.ts(7, 5): The expected type comes from property 'typeFn' which is declared here on type 'AutoMapOptions'

WeekDay is an enum with number value. If I remove Workday's constructor, there's no error. Do you know why is this happening?
Thanks in advance

[micalevisk]

how's your mapping (Mapper#createMap calls)?

[nartc]

Maybe your tsconfig isn't as strict

[micalevisk]

you're right! I'm using strictFunctionTypes: false + strict: false 👍

[lacoonte]

I don't know that much about TypeScript (I started using it recently), but wouldn't it be possible to constraint the constructor arguments in Constructible to the ones of the class' constructor? (Maybe using reflection)

[lacoonte]

I found this, don't know if it is possible to use it https://www.typescriptlang.org/docs/handbook/utility-types.html#constructorparameterstype

[nartc]

@alvarorece it is possible but it's not necessary for the case of @AutoMap and Constructible. I've already created a bug to address this so it should be fixed in the next release.