redhat-developer / redhat-developer/vscode-java
Renaming a field causes a change in code behavior
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
[provide a description of the issue]
Environment
Operating System: Windows11
JDK version: 17
Visual Studio Code version: 1.88
Java extension version: 1.29
Steps To Reproduce
1.select "j"
2.click “Rename”
3. new name "i"
class A {
void m() {
int i = 0;
class B {
// rename j to i;
int j;
void k() {
j = i;
}
}
};
}
refactoring result:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the rename from j to i using the Java code and Windows 11, JDK 17, VS Code 1.88, and Java extension 1.29 described in the issue. Start at the Rename refactoring entry point and compare the resulting references with the source; done means renaming the field does not change the behavior of the local variable reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100