Add a new rule to enforce a method syntax #1598
Description
Recently I found out that the shorthand method syntax is looser type-wise than the non-shorthand syntax:
interface MyInterface {
fn1(num: number | undefined): void;
fn2: (num: number | undefined) => void;
}
const badObject: MyInterface = {
fn1(num: number) {}, // no error??
fn2(num: number) {} // error
}
const shouldBeBadObject: MyInterface = {
fn1(num: number) {}, // no error??
fn2(num: number | undefined) {}
}
const goodObject: MyInterface = {
fn1(num: number | undefined) {},
fn2(num: number | undefined) {}
}Would it make sense to add a new @typescript-eslint/eslint-plugin rule to enforce the non-/shorthand syntax?