Avoid non-inclusive terms in function and parameter names

This product is not supported for your selected Datadog site. ().
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Metadata

ID: java-inclusive/function-definition

Language: Java

Severity: Notice

Category: Best Practices

Description

This rule promotes inclusive language by flagging the use of potentially offensive or outdated terms in function and parameter names. Words like “blacklist”, “whitelist”, “master”, and “slave” carry historical and social connotations that can be exclusionary and lead to a less welcoming codebase. Adopting inclusive terminology improves code readability, reflects modern best practices, and fosters a more diverse and respectful development environment.

How to remediate

To fix this violation, replace the discouraged terms with their inclusive alternatives. For “blacklist,” use “denylist” or “blocklist.” For “whitelist,” use “allowlist” or “safelist.” For “master,” use “primary,” “main,” or “controller.” For “slave,” use “secondary,” “replica,” or “worker.” Applying these changes ensures your code aligns with contemporary language standards and promotes clarity without cultural bias.

Non-Compliant Code Examples

class MyClass {
    void blacklist() {

    }

    int method(int WhiteList) {

    }
}
class Blacklist {
    void blacklist() {

    }

    int BlackList(int WhiteList) {

    }
}

Compliant Code Examples

class AllowList {
    void allowlist() {

    }

    int AllowList(int AllowList) {

    }
}
https://static.datadoghq.com/static/images/logos/github_avatar.svg https://static.datadoghq.com/static/images/logos/vscode_avatar.svg jetbrains

원활한 통합. Datadog Code Security를 경험해 보세요