-
Notifications
You must be signed in to change notification settings - Fork 446
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
[Feature Request] Method Signature Refactoring #2104
Comments
It should be possible, but the tricky part is creating a UI around it. We could probably have a look at https://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/tree/org.eclipse.jdt.ui/ui%20refactoring/org/eclipse/jdt/internal/ui/refactoring/ChangeSignatureWizard.java as a start point. |
any news on this? |
I'm also anxiously awaiting this feature. How is feature work prioritized? Can we vote somewhere? |
This is now implemented in the Netbeans language server plugin: https://marketplace.visualstudio.com/items?itemName=ASF.apache-netbeans-java That plugins has other issues however, so I hope we will get this soon. |
I'll take a look these days. |
we have an upstream PR: eclipse-jdt/eclipse.jdt.ui#428 which will make the processors available in jdt.ls. |
All prevalent IDEs such as Eclipse, IntelliJ, Netbeans provides a way to refactor method signatures.
It would be nice to have such a feature implemented in VSCode since the methods are usually spread across the entire project, and currently no such refactoring actions are supported(checked the documentation and opened/closed issues).
Visual Studio seems to have such an existing feature
Thank you for the hard work.
The text was updated successfully, but these errors were encountered: