Teddytrombone
commented
4 weeks ago The VS Code extension is more or less just a dumb LSP client for connecting to the actual TYPO3 LSP. In fact you could use any generic LSP client extension which allows to connect to any LSP server. It just makes some things easier by detecting the TYPO3 CLI binary to start the LSP, but this is mostly based on my experience in my development environment.
Depending on your TYPO3 configuration you might find some more useful data in the TYPO3 log. If the extension's LSP command can be executed successfully but there is any exception thrown, there should be an output in the VC code error console. If it's not, it looks like the command couldn't be started sucessfully.
As I just use Linux I cannot tell if there are any adaptions needed to get this working inside WSL and/or ddev. Maybe you need some wrapper script to get things started in a correct manner. You could try to create a script which calls the TYPO3 CLI binary and point the extension to it.
I will try to get my hands on a Windows 11 machine but I don't know when this will be the case. As it seemed that there was not much interest in an LSP for Fluid or TYPO3 in general when I applied for community budget, progress is very slow at the moment 😳
The TYPO3 extension is installed, but this error
Connection to server is erroring. Shutting down server.keeps persisting in the output. Is there a way to get a more useful error for debugging? Using latest WSL2 Ubuntu and ddev v1.23.4.