You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the current PHP feature includes multiple VS Code extensions with overlapping functionality:
PHP Intelephense (bmewburn.vscode-intelephense-client) - Provides Intelephense PHP language server
PHP Extension Pack (xdebug.php-pack) - Includes zobo.php-intellisense PHP language server
PHP Tools for VS Code (devsense.phptools-vscode) - Provides another PHP language server
PHP Debug (xdebug.php-debug) - Included in xdebug.php-pack
Since this configuration hasn't been updated in about 3 years, I'm wondering if all these extensions are still necessary. Having three extensions providing identical core functionality (IntelliSense and debugging) might cause multiple language servers to conflict with each other and create an unnecessarily bloated feature.
Would it make sense to clean up the extension list to reduce redundancy and potential conflicts?
Thanks for considering this suggestion!
The text was updated successfully, but these errors were encountered:
I noticed the current PHP feature includes multiple VS Code extensions with overlapping functionality:
bmewburn.vscode-intelephense-client
) - Provides Intelephense PHP language serverxdebug.php-pack
) - Includeszobo.php-intellisense
PHP language serverdevsense.phptools-vscode
) - Provides another PHP language serverxdebug.php-debug
) - Included inxdebug.php-pack
Since this configuration hasn't been updated in about 3 years, I'm wondering if all these extensions are still necessary. Having three extensions providing identical core functionality (IntelliSense and debugging) might cause multiple language servers to conflict with each other and create an unnecessarily bloated feature.
Would it make sense to clean up the extension list to reduce redundancy and potential conflicts?
Thanks for considering this suggestion!
The text was updated successfully, but these errors were encountered: