#PHPSTORM REVIEW CODE#
New in 3.0: More ‘Surround With’ actions for PHP Smart Duplicated Code Detector It’s described in detail in the IDE blog: If the format is not very suitable, generation templates can be corrected in your own way.Įditing templates of generation methods get * / set *. Simply describe the properties of the class, then call Code → Generate → Getters and Setters, and choose for which properties we should generate methods.Īnd here is the result of our «quick and easy» works. New Rename refactoring features in PhpStorm 2.0 Getter/SetterĮssences in Doctrine 2 (while using annotations for their announcement) give an illustrative example where the automatic generation of accessors / mutators is greatly helpful. Renaming mechanism, is anyone here could do without it? It is clearly described in the IDE blog, so I will not be repetitive: All we need is just hit Enter to admire the result. The name of the constant was suggested by IDE itself. The same principle can be used to allocate frequently repetitive lines in constants. You can set the visibility of properties, as well as a place where to declare it (in the current method, description of class or in the constructor). This function works similarly, it only adds a property of the class instead of variable.
Put the cursor somewhere nearby, run Refactor → Extract → Variable.), but this time instead of the dialog box, a drop-down list appears from which we can choose the appropriate block of code. As a result the code is much clearer and it’s easier to understand the logic in these conditions.Īnd if you’re too lazy to manually allocate piece of code to export to a variable - the storm can do it as well. We proceed similarly with the rest of the code. Here the meaning is not clear right away, and formatting this code is an inconvenient procedure.Īnd run Introduce Variable ( Refactor → Extract → Variable.), enter the name of the variable in the appeared dialog. For example, we have such section of code: The blog IDE gives such an example, but I use this functional a little differently. In that box we need to somehow call our method, to specify its visibility and sort out the order of the arguments, if necessary.īy the way, personally I use this dialog to determine the dependency of the «external» variables for an arbitrary piece of code that is very helpful in complex refactoring.Ī few more examples: ‘Extract Function/Method’ refactoring for PHP Introduce Variable
Such automatic checks are very useful in case of refactoring any large piece of code, for example, like in a loop:Īfter we identified the safe piece of code and run Extract Method, a dialog box appears. Hah, I accidentally allocated break at the end of the block, IDE noticed it smartly, and prevented me from a sad mistake. where could be this Extract Method, and what are its hotkeys: \Īnd while the use does not come to automatism – let’s remember about the universal code Find Action, which is perfect for finding the action even by the part of its names. Select our sheet code and… vaguely start remembering. Here you are, for example, a wonderful piece of code that just asks for decomposition. Works - don’t touch! And now let’s try this, but using IDE. And how many those bugs will appear in the process? No, down with this damned refactoring. Still what a hard job it is to allocate manually comparatively integral separate part, form it in a separate method, arrange all the necessary variables and write them into arguments, add the returned values in the newly invented method. We could always come across some sections of code where the methods would grow to such an extent that even-booze-shots-would-not-help. (or Help → Find Action., even if this one is forgotten). To execute any command in the storm, call any function, and spy any shortcut - it’s enough to remember only one key combination: Shift+ Ctr/⌘+ A I’d like to start with a small remark about refactoring of code.
#PHPSTORM REVIEW FREE#
Some time ago I have even replaced free NetBeans with paid PhpStorm that has better implementation of refactoring.
Fortunately, modern IDE are able to take part of the tasks for themselves while the developer can concentrate on the process of refactoring of code and architecture as a whole, rather than on the fight against boring code. And in the end there still may remain a lot of syntax errors. PHP refactoring is really cool! But in the process of fulfilling it, some routine operations and repetitive actions with the code are rather frequent.
0 kommentar(er)
