method parameter types defined in an interface doesn't apply to an actual class method parameters

[Jakhongiirr]

###

We don't want to define a type for both in interface and in class as we work with complex nested generic types

we want to see the error during coding, not at compile time

🙁
Current behavior:

interface A {
  method(param: string): void;
}

class B implements A {
  method(param): void {
    // the type of param is any
    console.log(param);
  }
}

const b = new B();
b.method(1); // -> no error

```

🙂
Expected behavior:

interface A {
  method(param: string): void;
}

class B implements A {
  method(param): void {
    // should be type error for param
    console.log(param);
  }
}

const b = new B();
b.method(1); // -> should be type error

[fatcerberus]

This already is an error:

Playground

Parameter 'param' implicitly has an 'any' type.

Make sure you have noImplicitAny (or preferably, strict) enabled.

[MartinJohns]

Duplicate of #32082.

[Jakhongiirr]

even after strict and noImplicitAny enabled, this is still an issue, sorry if it is duplicate, it is hard to analyze 5k+ issues

[typescript-bot]

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.