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:
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{//
}functionfoo(){consttest={};}
シームレスな統合。 Datadog Code Security をお試しください
Datadog Code Security
このルールを試し、Datadog Code Security でコードを解析する
このルールの使用方法
1
2
rulesets:- javascript-best-practices # Rules to enforce JavaScript best practices.