![]() Without most of these wonderful PHP-focused features, it'll be hard to recommend using something other than PHPStorm, even if it's slower and costlier and uses more memory. Please note: There are a million other features that PHPStorm uniquely offers, but to be honest, it's the tiny little conveniences that I've seen provide the biggest boost in efficiency.Īlso note: This is Sublime Text 3 we're talking about. ![]() Let's start with a quick list of ways that PHPStorm really sets itself apart for me. We love the code intelligence we get from PHPStorm, but still miss the speed, quick boot-up, and convenience of Sublime Text.īefore I blindly assume PHPStorm is the only way to go, I wanted to see: Can I bring the things a PHP-focused IDE provides PHP developers back to Sublime Text and get the best of both worlds? There are tons more, but a lot of them have already been mentioned.A lot of folks in the PHP community have been checking out PHPStorm lately, including myself and most of the developers I work with. Setting all of your PHPDoc with proper types will give you much better code insight and warnings about what methods expect.Ĥ) Definitely turn on code inspections on code commit, this will help you find a ton of subtle bugs especially if you keep your PHPDoc up to date.ĥ) The Right Click Refactor menu (and learning the Extract Method/Extract Variable/Refactor Rename shortcuts) is amazing in its power.Ħ) Ctrl-A to find the keyboard shortcuts of the hundreds of PHPStorm features.ħ) Ctrl-Shift-F Find in files is very powerful and usually very fast (everything gets indexed by PHPStorm).Ĩ) The Regex tester plugin can save a bunch of time (though there are better stand alone tools).ĩ) Test Restful Web Service is very powerful, though I wish you could use it to debug your own REST services without having to manually setup the Xdebug/ZendDebugger variables.ġ0) The built in PHPUnit runner (though I wish you could configure the VCS commit to force a run of PHPUnit before allowing a commit).ġ1) Speaking of which the VCS commit window which allows for things like auto-format/optimize imports/seach for TODO's/run inspections.ġ2) Live Edit is pretty neat, but more useful if you are developing straight HTML rather than dynamic PHP. I consider a code formatter that rewrites the control flow of the program to be broken - even if it is an option that can be disabled.ġ) Ctrl-Shift-V to access to clipboard ring.Ģ) Local History of a file can be VERY useful if you break something between VC commits.ģ) Alt-Insert brings up the generate menu (to generate getters/setters, and PHPDoc). It shouldn't be considered a "styling" thing that a code formatter handles. Something like that is something the interpreter/compiler should optimize away. Unset($temporary_function_result_123abc) ![]() I would consider what we're talking about functionality equal to having the following code: foreach (someFunctionThatReturnsAnArray() as $item) Similar to how $i++, $i += 1 are the same functionally, but they tend to be used differently. The programmer may have purposely wanted an if statement to be contained within the else statement for their own reasons (ex: easier to add logging for debug reasons even if the second if condition fails). The end result is the same, of course, but what the programmer actually wrote has been changed beyond stylistic properties.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |