redhat-developer / redhat-developer/vscode-java
Refactoring extraction methods leads to syntax errors.
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:
- select " this.value = value;"
- click “Refacator-Extract to method”
class ExtractMethodTest {
private final int value;
public ExtractMethodTest(int value) {
// extract method
this.value = value;
}
}
refactoring result:
Reason: The final field ExtractMethodTest.value cannot be assigned
Expected behavior: Check before and after refactoring, and issue a warning if there are syntax errors
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
Start by reproducing the extraction-method refactoring on the Java snippet with JDK 17, VS Code 1.88, and Java extension 1.29. Trace the extraction refactoring entry point and its validation flow, then verify that invalid output is detected and a warning is issued rather than silently producing syntax errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100