Moving code around is an essential part of application design and maintenance, but it may become a tedious task in modern code utilising namespaces and the PSR0 file layout convention. Move Class refactoring is a reliable tool that will remove the burden of maintaining project consistency and allow you to use move as a simple atomic action, allowing you to keep your focus on the design decisions, that is especially important as a part of complex high-level refactorings. (more…)

Moving code around is an essential part of application design and maintenance, but it may become a tedious task in modern code utilising namespaces and the PSR0 file layout convention. Move Class refactoring is a reliable tool that will remove the burden of maintaining project consistency and allow you to use move as a simple atomic action, allowing you to keep your focus on the design decisions, that is especially important as a part of complex high-level refactorings. (more…)

The easiest way to enhance code readability is to standardize its organization. For example, you can specify methods to be ordered after fields or keep dependent methods together. The good news is that starting with version 6, you can have your code rearranged automatically! All code generated by PhpStorm will follow these rules, so you don't have to worry about it at every turn. (more…)

The easiest way to enhance code readability is to standardize its organization. For example, you can specify methods to be ordered after fields or keep dependent methods together. The good news is that starting with version 6, you can have your code rearranged automatically! All code generated by PhpStorm will follow these rules, so you don't have to worry about it at every turn. (more…)

As you work on a big project, you often face the need to refactor your code to maintain it properly. Likewise, there are many situations when you start to add functionality from the bottom of the class hierarchy and then realize it can be also used in more common cases (otherwise some parts of your code may become obsolete for the parent class but still be valid for one of its children). To fix this, you copy a method or field from one class, paste it into another and fix internal references in the member. This isn't so difficult, yet rather annoying if done over and over. With PhpStorm,

As you work on a big project, you often face the need to refactor your code to maintain it properly. Likewise, there are many situations when you start to add functionality from the bottom of the class hierarchy and then realize it can be also used in more common cases (otherwise some parts of your code may become obsolete for the parent class but still be valid for one of its children). To fix this, you copy a method or field from one class, paste it into another and fix internal references in the member. This isn't so difficult, yet rather annoying if done over and over. With PhpStorm, bot