Renaming fields causes conflicts with variable naming, resulting in changes in code behavior

[DongChunHao]

[provide a description of the issue]

Environment

• Operating System:
• JDK version:
• Visual Studio Code version:
• Java extension version:

Steps To Reproduce

1.select "originalField"
2.click “Rename”
3. new name "originalFieldRenamed"

class MyClass {
// rename "originalField" to "originalFieldRenamed"
private final int originalField = 10;
protected int protectedField;

public void myMethod() {
int originalFieldRenamed = 20; // Local variable with the same name as the field
System.out.println(originalField);
}
}
refactoring result:

[github-actions]

We have found issues that are potential duplicates:

• Renaming fields causes conflicts with parameter naming, resulting in changes in code behavior #3614 (93.33%)

If any of the issues listed above are a duplicate, please consider closing this issue & upvoting/commenting the original one.
Alternatively, if neither of the listed issues addresses your feature/bug, keep this issue open.

[gtn1024]

It seems IntelliJ have the same behavior.