-
Notifications
You must be signed in to change notification settings - Fork 286
Support goto definition for bundled gems ? #111
Comments
Is there a way to navigate to the external gem libraries outside workspace for methods and classes. i.e the gem libraries which are inside ruby installed folders. |
I usually have 3 way for thiswith Bundler$ bundle show "GEM_NAME_HERE"
#=> returns path to the used requested gem + click on it in the vscode terminal with ruby built in Object#methodp object_that_method_intrests_me.method(:method_name_here).source_location Ruby RipperThis is a little more complex, it's a core package that allows you to parse ruby sources, and with that you can search between the tokens that includes the definition representation too. |
I have the same problem |
Closing for issue cleanup. Apologies if this is still an issue. We are working to improve the core extension experience. |
Is there any intention to fix this? I have just run into it, the way I have gotten around it is to set BUNDLE_PATH and GEM_HOME to vendor/bundle and ensure the gems are installed within the workspace root, but this is not ideal. |
I think its a really important feature. Is there any plan to open it? |
@rajagopalsubhash I had a PR merged a while ago now that should have fixed the issue of stepping into gems installed outside the workspace root: #350 |
@wingrunr21 Please reopen, this is a valid feature request. @stefansedich It doesn't seem to be usable at this moment: |
please reopen issue/feature request... |
Install solargraph, follow the instruction here |
please reopen issue/feature request... |
Your environment
vscode-ruby
version:Expected behavior
it would be nice to have some way to make the goto definition work with bundled gems
such as using the
bundle list --paths
paths to scan references in gems or anything like that.The text was updated successfully, but these errors were encountered: