redhat-developer / redhat-developer/vscode-java
Inline method refactoring leads to syntax errors with IOExp
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 "originalMethod()"
2. click “Refacator-inline method”
public class OriginalClass {
public void originalMethod() throws IOException {
}
}
public class OtherClass {
public void callerMethod(){
OriginalClass obj = new OriginalClass();
try {
obj.originalMethod();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
refactoring result:
Expected behavior: Check for grammar issues before and after inline refactoring, and provide warning prompts
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 failure in the VS Code Java extension using the provided OriginalClass and OtherClass example, then inspect the inline method refactoring entry point. Done means the refactoring no longer produces syntax errors and clearly warns when the source or result has grammar issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100