For a plaintext version of this page, see: https://docs.datadoghq.com/security/code_security/static_analysis/static_analysis_rules/typescript-best-practices/no-empty.md
This product is not supported for your selected Datadog site. ().
Metadata
ID:typescript-best-practices/no-empty
Language: TypeScript
Severity: Error
Category: Best Practices
Description
Empty or non-functional blocks in the code can be misleading and lead to maintenance difficulties. They can also lead to a false sense of security or functionality. While they may not directly introduce security issues, their presence can suggest that some logic or error handling is implemented when it is not.
You can avoid this problem by including a comment to indicate that you intend to leave the block empty. For example:
exportasyncfunctionfoo() {consttest={};}if(foo){bar()}while(foo){bar()}for(;foo;){bar()}try{foo()}catch(ex){foo()}switch(foo){case'foo':break;}if(foo){/* empty */}while(foo){/* empty */}for(;foo;){/* empty */}try{foo()}catch(ex){/* empty */}try{foo()}catch(ex){// empty
}try{foo()}finally{// empty
}try{foo()}finally{// test
}try{foo()}finally{// hi i am off no use
}try{foo()}catch(ex){/* test111 */}if(foo){bar()}else{// nothing in me
}if(foo){bar()}else{/**/}if(foo){bar()}else{//
}constexample=useState(()=>{});