Avoid avoiding a variable to itself

Docs > Plateforme de sécurité Datadog > Code Security > Static Code Analysis (SAST) > Règles SAST > Avoid avoiding a variable to itself

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Metadata

ID: apex-code-style/self-assign

Language: Apex

Severity: Info

Category: Best Practices

Description

This rule detects assignments where a variable is assigned to itself, such as foo = foo;. Such statements are redundant and have no effect on the program’s state. They can indicate a mistake or misunderstanding in the code logic.

To comply with this rule, review assignments and ensure that each variable is assigned a meaningful or updated value. If the intent is to update a variable, use expressions that modify or transform its value, for example, foo = foo + 1;. If you are performing self-assignment to avoid leaving a parameter unused, you should be more explicit and assign it to a new variable, for example String ignore = unusedParameter.

Non-Compliant Code Examples

class Class {
    public void myFunction(){
        Integer foo;
        foo = foo;
    }
}

Compliant Code Examples

class Class {
    public void myFunction(){
        Integer foo;
        foo = foo + 1;
    }
}