- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
ID: java-best-practices/default-label-not-last-in-switch
Language: Java
Severity: Notice
Category: Best Practices
The widely adopted convention is putting the default
statement at the end of a switch
statement. By adhering to this practice, your code becomes more comprehensible and predictable for developers who engage with it in the future.
public class Foo {
void bar(int a) {
switch (a) {
case 1:
break;
default: // this should be the last statement
break;
case 2:
break;
case 3:
break;
}
}
}
public class Foo {
void bar(int a) {
switch (a) {
case 1:
break;
case 2:
break;
}
}
}
public class Foo {
void bar(int a) {
switch (a) {
case 1: // do something
break;
case 2:
break;
default: // the default case should be last, by convention
break;
}
}
}
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products