Unexpected empty async method 'delete'
26
27 async update(){}
28
29 async delete(){} 30}
31
32class ClientRepository extends Repository {
Unexpected empty async method 'update'
24
25 async findOne(){}
26
27 async update(){} 28
29 async delete(){}
30}
Unexpected empty async method 'findOne'
22
23 async findMany(){}
24
25 async findOne(){} 26
27 async update(){}
28
Unexpected empty async method 'findMany'
20
21 async create(data){}
22
23 async findMany(){} 24
25 async findOne(){}
26
Unexpected empty async method 'create'
18 console.log(`hello from ${Object.getPrototypeOf(this).constructor.name}`);
19 }
20
21 async create(data){} 22
23 async findMany(){}
24
Unexpected empty async method 'delete'
13
14 async update() {}
15
16 async delete() {}17}
Unexpected empty async method 'update'
11
12 async findByID() {}
13
14 async update() {}15
16 async delete() {}
17}
Unexpected empty async method 'findByID'
9
10 async findMany() {}
11
12 async findByID() {}13
14 async update() {}
15
Unexpected empty async method 'findMany'
7
8 async create() {}
9
10 async findMany() {}11
12 async findByID() {}
13
Unexpected empty async method 'create'
5 }
6 }
7
8 async create() {} 9
10 async findMany() {}
11
Description
Having empty functions hurts readability, and is considered a code-smell. There's almost always a way to avoid using them. If you must use one, consider adding a comment to inform the reader of its purpose.
Bad Practice
getUser('SwaGaLisTiQuE', () => {})
function f() {}
Recommended
getUser('SwaGaLisTiQuE', () => {
// empty because <reason>
})
function f() {
// intentionally empty. <reason>
}