I don't think you should make this modification at all.

The current file link format is based on https://github.com/aik099/PhpStormProtocol, but PHPStorm supports the protocol natively using a different syntax (Since PHPStorm 8)

It appears this is only true for PHPStorm 8 on MacOS. Windows and Linux versions of PHPStorm still require https://github.com/aik099/PhpStormProtocol (or https://github.com/sanduhrs/phpstorm-url-handler on Linux). The documentation even references PhpStormProtocol as a requirements for using the 'phpstorm' value for 'ide'.

Perhaps, there should be a new 'phpstorm-mac' value in the code with the new format ('phpstorm://open?file=%f&line=%l') and the documentation should be changed to have a generic example such as 'myide://open?url=file://%%f&line=%%l' to avoid confusion with phpstorm.

In my particular case, I would have had zero problems if I had just set the value of the 'ide' to 'phpstorm'. My mistake was seeing 'phpstorm://open..." in the example for another editor and using that misleading example instead.

I've updated the PR to only change the value in the case of Mac. I'm not close to a Windows PC at the moment, but I'll double check Windows and Linux tomorrow.

I think the docs should be updated to mention specifically using https://github.com/aik099/PhpStormProtocol and https://github.com/sanduhrs/phpstorm-url-handler on Windows and Linux respectively (instead of just specifying that PhpStormProtocol is needed) and the examples should change to myide like you mentioned

I updated the docs as suggested into symfony/symfony-docs#7513

I double checked Windows and Linux, and this PR is ready.

Status: Needs Review

Changed the config to use a separate key to cater for VMs

@harcod Can you please make the changes to the docs PR to use phpstorm-core instead

I'm probably too late, but ... what if we change these values as follows:

The reason is that ultimately PHPStorm will do the right thing and support their correct native format ... so that should be phpstorm and not phpstorm-<something>

Won't that be a BC break, for everyone using phpstorm currently and now getting a different value?

I agree phpstorm should be the official value that PHPStorm supports, but there is no indication when it will be added to the other platforms. So when that happens, maybe phpstorm-core can be deprecated and removed in the next major with phpstorm holding the official value?

I don't think there is such a thing as BC break for such a parameter. It has no impact on user's code.

It doesn't have an impact on the code, but it has an impact on the current experience and expectations. It would still require a change in the config to keep the current experience. But if you think thats not a problem then I'm happy to make the change

I think that's definitely something we can do in a minor release, with a proper entry in the changelog.

I have submitted PRs to the Windows and Linux versions of the phpstorm protocol handlers that would allow them to support both the native PhpStorm Mac scheme as well as their current scheme. If these are incorporated, then this PR could just eliminate the "phpstorm-protocol" completely and only support the native PhpStorm format.

Since both PRs have been merged, we only need to support the official format. I have updated the PR accordingly

So, this new version of the PR should be merged into 2.7 as a bug fix, right?

@fabpot The phpstorm helper was only added in 3.2.

I stuffed up my branch, so I created a new PR to go as a bugfix against 3.2 #21813