Open james-ball-qualcomm opened 2 days ago
In my experience, the LSP extension still has a lot of issues. I recommend using Solargraph, which also gets you intellisense, instead until they are fixed.
The ruby debugger can run in vscode, you just have to let vscode know how to run Ruby in the container. We can talk about it on the phone, and then perhaps you can post a how-to.
It's pretty painful to debug UDB Ruby code given that the main-stream Ruby debugger and IDE (Ruby LSP) doesn't run in the container setup used by UDB. Having to do printfs (or in Ruby puts) to debug the UDB Ruby code is a productivity impediment. Can we figure out how to get some Ruby debugger and IDE to run in UDB's environment?