Why does it bundle koichisasada.vscode-rdbg when Shopify.ruby-lsp supports debugging?

[Nowaker]

This is really unclear. Shopify.ruby-lsp supports debugging. And this extension pack depends on koichisasada.vscode-rdbg. So what should I use to debug? Shopify.ruby-lsp or koichisasada.vscode-rdbg? If the answer is Shopify.ruby-lsp, then this plugin should no longer bundle koichisasada.vscode-rdbg. And if the answer is koichisasada.vscode-rdbg, then why does Shopify.ruby-lsp support debugging?

[vinistock]

Thank you for the question.

The Ruby LSP's debugger client doesn't yet support all features available in RDBG. We started out with some of the main debugging flows, especially so that we could connect the debug code lens that appear on tests to the debugger client.

Eventually, when the Ruby LSP matches feature parity, we can remove RDBG from the extension pack.

Meanwhile, if the Ruby LSP is sufficient for your needs and you haven't found an RDBG feature we don't support, you can uninstall RDBG and the extension pack will not automatically re-install it.

[Nowaker]

Thank you for your explanation, @vinistock. Perhaps this type of explanation could be included in the pack's description?

Also, since koichisasada.vscode-rdbg doesn't tap directly into Shopify.ruby-lsp's Ruby version manager detection system, bundler support etc, perhaps the readme of this plugin could include a launch.json example to use when coupled with Shopify.ruby-lsp?

[vinistock]

Perhaps this type of explanation could be included in the pack's description?

Sure, I think that's a good addition.

...perhaps the readme of this plugin could include a launch.json example to use when coupled with Shopify.ruby-lsp?

The Ruby LSP doesn't interact with RDBG in any way. I think RDBG specific documentation should probably be centralized in its own repo.

That said, we can definitely include a link to their documentation in our explanation of the debugger clients.

Let me know if you're interested in putting a PR up for these.