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
Thank you for the feature suggestion. Can you give me an example launch.json?
I don't believe you need those configurations at all. The Ruby LSP hooks into your version manager to activate the Ruby environment, which means it should be able to find Bundler without you having to specify the path to it.
And if you want to use Bundler when launching a Ruby script, all you have to do is including bundle exec as part of the program configuration.
I managed to figure out the "args" setting, but what to do with the "cwd" setting is unclear. And the resulting version of launch.json for your extension is like this:
Why do you need to set the cwd? Do you have multiple workspaces configured? And if that's the case, does moving the launch.json file inside that workspace fix the issue?
I have checked that this feature is not already implemented
Use case
We are planning to migrate from VS Code extension https://github.com/rubyide/vscode-ruby to your extension, but we are missing two settings in launch.json "pathToBundler" and "useBundler".
https://github.com/rubyide/vscode-ruby/wiki/2.-Launching-from-VS-Code#pathtobundler
https://github.com/rubyide/vscode-ruby/wiki/2.-Launching-from-VS-Code#usebundler
Description
Are there plans to add "useBundler" and "pathToBundler" settings to launch.json for debugging?
Implementation
No response
The text was updated successfully, but these errors were encountered: