But still there are some potential problems:
1. The variable already exists in the class. 2. You accidently mark to much or to few lines with ":<,>%"
For refactorings such as extract method the number of preconditions and information to gather is much bigger, such as input and output variables, existance of return statement etc.
We plan to integrate the tool into vim as well, so that you can call the refactorings through vim directly.
Edit: Also see the screenshot here for a more complex extract method refactoring: http://qafoolabs.github.io/php-refactoring-browser/
Similarely to the convert-local-to-instance-variable example, to me it looks like overkill. I never had a problem, doing these things manually. But if you like doing it this way - I dont complain. To each his own.
It's the difference between using hjkl for movement, and ignoring all the other commands vim as to offer. Why wouldn't want you to automate patterns in your work?
I'd love to see a tool like this start to support a bunch of complex refactorings, especially on a project level. With time, it could start to support a bunch of nice things which make it easier to use, such as aliases or readline support for auto-completion, etc. People may then write plugins or scripts for various editors such as vim to make various refactorings even simpler to use.
Of course, this is all wild speculation, but it is what I would love to see. I hope it works out very well, because I am a massive fan of the refactoring in the IntelliJ PHP plugin/PHPStorm.
When you leave vim and do this:
I stay in vim and simply do this: And hit y a couple of times.Pros:
I dont need to install, trust and learn a new tool.
I dont have to worry if i broke somthing. Because of edge cases the tool did not handle or because I messed up the syntax.