-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging support? #90
Comments
Currently there are no plans to incorporate debugging into vscode-solargraph. The good news, however, is that this extension and vscode-ruby should play well together. The overlapping features should be disabled in vscode-ruby by default. I use both extensions and haven't encountered any problems. |
That's good to hear. Is there cooperation between you and the vscode-ruby dev? Can we count on all the non-debugging features always being disabled by default in vscode-ruby? |
We've cooperated quite a bit, yes. There was even a brief time when vscode-solargraph was one of vscode-ruby's dependencies, but keeping them separate turned out to be more practical. It was always one of my goals to make sure the extensions are compatible because I didn't want to spend time duplicating their already solid debugger. |
Great! Thanks for spending that effort to cooperate with them. I'll install both extensions. |
I was wondering if there are plans to add debugging support to this extension.
There's another VS Code extension for Ruby (https://github.com/rubyide/vscode-ruby) that supports debugging but I prefer the code completion and refactoring features provided by Solargraph. They have plans to add features to their language server (rubyide/vscode-ruby#317) but their plans appear to lag behind the features this language server already has.
One thing I thought of was installing both extensions and trying to disable the other extension's features except for the debugging support, so that I could combine them, but I'm afraid of any side effects that might occur.
The text was updated successfully, but these errors were encountered: