-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
weird behavior of the Quick Fix; "Surround with try/catch" #2711
Comments
I'm able to reproduce as well. In fact, this is basically the same as https://bugs.eclipse.org/bugs/show_bug.cgi?id=36365 (which was fixed long ago), but if one applies the refactoring from the bottom-up it's still reproducible. |
Thank you. |
https://github.com/eclipse-jdt/eclipse.jdt.ui would be the place. Unfortunately it's not possible to transfer this issue from here to there although that probably would have been ideal. I mentioned the issue to @jjohnstn, who is also a committer there so there is some awareness of it. |
I will wait for it to be fixed. I appreciate it. |
The following issue has been opened: eclipse-jdt/eclipse.jdt.ui#353 |
Fix has been merged but the change for try/catch is in JDT UI and will need to either be refactored or copied for jdt-ls. The problem also existed for surround with try-with-resources and has been fixed as well. No refactoring needed for the second fix. |
I can have a look at what needs to be copied and adjust it. |
- See redhat-developer/vscode-java#2711 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
- See redhat-developer/vscode-java#2711 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
- See redhat-developer/vscode-java#2711 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
I found that it have been fixed. Thank you. |
[weird behavior of auto generate when generating try-catch]
Environment
Steps To Reproduce
Current Result
Even if this variable name "e1" were "e", it won't conflict any other variables.
Expected Result
Maybe (Exception e) is correct behavior.
Additional Informations
The text was updated successfully, but these errors were encountered: