Void operators found JS-0098
Anti-pattern
Minor
11 days ago
—
11 days old
Expected 'undefined' and instead saw 'void'
263 console.error('Error:', error);
264 }
265 setOpenModalDeleteVuln(false);
266 void fetchVulnerabilities();267 };
268
269 const deleteRegisterConfirmation = (item: TableData) => {Expected 'undefined' and instead saw 'void'
220 void fetchVulnerabilities();
221 void fetchLanguages();
222 void fetchTypes();
223 void fetchCategories();224 }, [fetchCategories, fetchVulnerabilities]);
225 //
226Expected 'undefined' and instead saw 'void'
219 useEffect(() => {
220 void fetchVulnerabilities();
221 void fetchLanguages();
222 void fetchTypes();223 void fetchCategories();
224 }, [fetchCategories, fetchVulnerabilities]);
225 //Expected 'undefined' and instead saw 'void'
218
219 useEffect(() => {
220 void fetchVulnerabilities();
221 void fetchLanguages();222 void fetchTypes();
223 void fetchCategories();
224 }, [fetchCategories, fetchVulnerabilities]);Expected 'undefined' and instead saw 'void'
217 }, []);
218
219 useEffect(() => {
220 void fetchVulnerabilities();221 void fetchLanguages();
222 void fetchTypes();
223 void fetchCategories();
Description
A return; statement with nothing after it is redundant, and has no effect on the runtime behavior of a function.
This can be confusing, so it's better to disallow these redundant statements.
Bad Practice
function foo() { return; }
function foo() {
doSomething();
return;
}
function foo() {
if (condition) {
bar();
return;
} else {
baz();
}
}
function foo() {
switch (bar) {
case 1:
doSomething();
default:
doSomethingElse();
return;
}
}
Recommended
function foo() { return 5; }
function foo() {
return doSomething();
}
function foo() {
if (condition) {
bar();
return;
} else {
baz();
}
qux();
}
function foo() {
switch (bar) {
case 1:
doSomething();
return;
default:
doSomethingElse();
}
}
function foo() {
for (const foo of bar) {
return;
}
}