Vscode-ruby: Support goto definition for bundled gems ?

[adamluzsi]

Your environment

• vscode-ruby version:
• Ruby version: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
• bundler version: 1.12.5
• VS Code version: 1.8.1
• Operating System: macOS Sierra

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.

[pnagaraja1]

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.

[adamluzsi]

I usually have 3 way for this

with 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#method

p object_that_method_intrests_me.method(:method_name_here).source_location

Ruby Ripper

This 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.

[zouchao]

I have the same problem

[wingrunr21]

Closing for issue cleanup. Apologies if this is still an issue. We are working to improve the core extension experience.

[stefansedich]

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.

[rajagopalsubhash]

I think its a really important feature. Is there any plan to open it?

[stefansedich]

@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: https://github.com/rubyide/vscode-ruby/pull/350

[Nowaker]

@wingrunr21 Please reopen, this is a valid feature request.

@stefansedich It doesn't seem to be usable at this moment:

[batamire]

please reopen issue/feature request...

[ndan]

Install solargraph, follow the instruction here

[loohawe]

please reopen issue/feature request...