editorconfig to PhpStorm (also used by the TYPO3 core). editorconfig it’s possible to enforce project coding standards without everyone having to carefully configure their editors or IDEs. Besides the glance feature, for me it mostly provides a bigger scroll bar which I can’t miss. Read more CodeGlanceĬodeGlance adds a minimap for code as known from sublime to the editor. Helpful for those of us, who do labels last. The plugin helps extract hard-coded strings to TYPO3 XLIFF files by simply highlighting the text and clicking extract. Read more about the TypoScript and Fluid plugins. The premium version is ad-free and supports further development efforts. The plugins are free with advertisement in a basic version. Sgalinski is offering both a TypoScript and a Fluid plugin, providing auto-complete and code-formatting capabilities for both. Creating Fluid Styled Content Elements.Ĭedric Ziel is providing the plugin for free and as open source, please consider donating if it’s useful for you.TYPO3 specific inspections and types (GeneralUtility::makeInstance return values among others).The one must-have plugin when developing TYPO3 with PhpStorm is the TYPO3 CMS Plugin. It takes some time to get used to it, but once you do, it’s an amazing tool.Īside from the core functionality PhpStorm provides, there are also some plugins I’m regularly using-both TYPO3 specific and not. For example, when setting a breakpoint the PhpStorm debugger console allows you to not only inspect the current context but also to execute PHP in that context - calling a method, evaluating a condition and whatever else seems necessary. Do not var_dump/echo your way through the code - you will be much more efficient with a debugger as you can see more context, see the stack trace as well as evaluate code at a specific point of time. Additionally, when generating coverage in the IDE you can highlight uncovered code lines in the editor, making it easy to see missing tests while staying focused on the code. Running tests inside the IDE has the advantage that you can directly jump to offending code if tests fail as the files are linked in the info window. ![]() While it doesn’t make you a better programmer, it gets you where you want to be faster and makes it a lot easier to follow code structures-for example when debugging an issue. ![]() ![]() Learn how to get around in your code base: Make use of Navigate to File/Class/Symbol, learn how to open the file browser at the location of any file with a shortcut, find out how to quickly switch between test and implementation and navigate between the usages and declaration of a method with no more than a keystroke. With Code > Generate (or in my case Alt+Insert in a file) you can additionally generate some common code/comment parts like getters/setters, copyright notices, or PHPDoc. There are some configured by default but you can also add your own for code you use often. For example writing “$apples.fe” and pressing tab results in “foreach ($apples as ) ”. Live templates allow you to create custom shortcut code that expands to bigger snippets. I’m a big fan of two-key shortcuts-for example I have configured: Some of my most used shortcuts areĪdditionally, I would recommend creating your own keymap for shortcuts with ones you can easily remember. PhpStorm can do many things that make your development faster-and nearly all of it can be mapped to a shortcut. When you are trying PhpStorm-or working with it-consider these tips to make the most of it: Learn Shortcuts
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |