Visual Studio Code: 'vscode://file/%%file%%:%%line%%'.Here’s how the parameter can be set in the configuration file: parameters :ĮditorUrl : 'phpstorm://open?file=%%file%%&line=%%line%%'Įxamples of URLs for the most common editors are: ✏️ phpstorm://open?file=/home/dev/test.php&line=3

The default table error formatter offers a configuration parameter editorUrl that lets you specify a URL with placeholders that will be printed next to the error message in the output: -ģ Parameter #1 (stdClass) of echo cannot be converted to string. You can change the default error format in the configuration. You can also implement your own custom error formatter.

teamcity: Creates TeamCity compatible output.

gitlab: Creates format for use Code Quality widget on GitLab Merge Request.

github: Creates GitHub Actions compatible output.Note that you’d have to redirect output into a file in order to capture the results for later processing. junit: Creates JUnit compatible output.json output with whitespaces and indentations. checkstyle: Creates a checkstyle.xml compatible output.raw: Contains one error per line, with path to file, line number, and error description.Additionally, the table formatter will detect it runs in a Continuous Integration environment like GitHub Actions and TeamCity, and besides the table it will also output errors in the specific format for that environment. You can pass the following keywords to the -error-format=X CLI option of the analyse command in order to affect the output: PHPStan supports different output formats through various so-called error formatters.

Gitlab phpstorm