VS Code Setup

As of August 2021, we will be terminating our license with PHPStorm in favour of VS Code. Over the years VSCode has come a very long way from the basic code editor it used to be at it's infancy, and it's become one of the leading tools that developers rely on for all sorts of projects.

Out of the box, VS Code runs faster than it's Java-based counterparts, and uses a fraction of the resources when compared to full-blown IDEs. Resources aside, PHPStorm and other IDEs spend a lot of time indexing your projects, getting in the way of development and slowing down your workflow.

Out of the box, PHPStorm comes with various tools that make it one of the best IDEs out there. There's no denying that PHPStorm is a great piece of software, however due to the wide adoption of VS Code, and the large number of official extensions, one can easily switch without skipping a beat.

A quick peak at the Activity Monitor shows the massive difference in resources between the two applications:

Here's a list of extensions that we highly recommend to Elentra developers:

Visual Studio Code Keyboard Shortcuts

It's better to learn VS Code's default key-bindings, however, some developers might prefer to maintain PHPStorm's key-bindings in VS Code, and for that, you can use IntelliJ IDEA Keybindings.

You can access a list of shortcuts for your operating system by going to Help - Keyboard Shortcuts Reference within your VS Code application, or click here.

PHP in Visual Studio Code

Click here to read a general overview of PHP programming in VS Code with tips around linting and debugging.

Additional Helpful Customization

Initially, you may find the visual layout a bit challenging, especially if you've been using PhpStorm for a long time. There are many small visual differences things that seem insignificant, but they do make a big difference. We recommend you spend some time in the Settings and configure the interface to something you're happy with.

Working tree file/folder indentation

Settings - Workbench > Tree: Indent (Controls indentation in the Workspace tree)

Increase the size of variables that you can peak at when using breakpoints

"xdebugSettings": {
    "max_children": 999,
    "max_depth": 10,
    "max_data": -1

Last updated