You can also select the whole file in the editor and choose “Exclude Lines from the commit” action from the context menu.
#Phpstorm wrap text code#
When you have a lot of changes in a file, but you only want to commit a few of them, use the new Uncheck all checkbox to uncheck all the code chunks at once, and then recheck only the ones you want to commit.Īlso, please note that you can always uncheck a file in the tree, in which case it will exclude all the changes in it from the commit. We’ve just made partial commits a little easier to use. This can be useful when there are some work-in-progress parts that you don’t want to commit yet, or if you want to split changes into several logical commits. By using the checkboxes in the Diff pane of the Commit Changes dialog, you can selectively add only some specific code changes into a commit. New “Uncheck all” checkbox for partial Git commits
If you are switching from Sublime Text and would like to use the same set of shortcuts, go to Preferences | Keymap and from the Keymap list, select Sublime Text. Now it’s Sublime Text’s turn to have its keymap available out of the box in PhpStorm. This is why we are continuing to add new pre-configured keymaps. Switching over from another IDE can be tough, especially if you’ve been using for a while and are accustomed to its keyboard shortcuts. The feature is disabled by default, so make sure to check out Preferences | Editor | General | Soft Wraps and set it up as needed. In this release, we’ve added the ability to set up a list of file types that will be soft-wrapped automatically. Activating it manually every time can be annoying. For example, you need it for markdown or plain text files, but not for PHP code. Sometimes you may need to have soft-wraps for one kind of files but not for others. To activate it for the currently opened file, go to View | Active Editor | Use Soft Wraps. In PhpStorm you can use soft-wraps to handle the appearance of long lines in your code. Now you can select the Enable for all files checkbox in PHP | Type compatibility | Strict type checking rules violation inspection that will emulate declare(strict_types=1). Let’s say you would like to introduce strict type checking into your project, but at the same time, you want a smooth transition that ensures the working application along the way. Strict type rules violation inspection for all files In such cases, it will suggest leaving the right-hand side as it is. The quick-fix is smart enough to detect situations when the assignment expression may have side effects. PhpStorm 2019.1 introduces a new quick-fix that helps you get rid of the unused variables that appear in assignments and closures’ use lists.
PhpStorm had the Unused variable inspection for a long time, but still provided no convenient way to remove the variable. To have the best from both worlds, we’ve introduced a lifecycle management option for Docker Compose: However, this approach also has some downsides: It doesn’t support containers that don’t work in daemon mode (that is, stop right after the start). In previous PhpStorm 2019.1 EAP builds, we’ve changed the default execution method for the Docker Compose based interpreters from docker-compose run to docker-compose exec. This solved the problem with heavy containers, which were forced to restart on each test run.
#Phpstorm wrap text Patch#
Or, if you have the previous PhpStorm 2019.1 EAP build (191.5109.15) installed, you should soon get a notification in the IDE about a patch update.ĭocker Compose: Container lifecycle management
#Phpstorm wrap text download#
You can download it on the website or via JetBrains Toolbox App. This build delivers the ability to enable soft-wraps depending on file type, a new “Uncheck all” checkbox for partial Git commits, a Sublime Text keymap, and more!