-
Notifications
You must be signed in to change notification settings - Fork 286
Go to definition not working in 0.15.0 for VS Code - Insiders #209
Comments
Any feedback on this issue? |
I think you mistyped:
|
This is broken for me as well. |
Any updates on this? I am on VS code version 1.19.3 and on |
#248 is a step toward resolving this issue. The next version of the Solargraph extension will include support for going to a definition in any file in the workspace. |
Doesn't work in 1.21.1 for me |
It doesn't work for me too! You can install https://github.com/MiguelSavignano/vs-code-ruby-symbols but it works only for file :( |
Check which option you're using for If you use A related solargraph bug due to character encoding issues is being tracked at castwide/vscode-solargraph#32. |
@castwide I use solargraph, I'll wait fixing of related bug that you provided. Thank you |
I fixed this by installing the |
Gem version 0.17.4 is published. It resolves the character encoding bug that caused "go to definition" to stop working in some workspaces. |
It still shows |
Sorry, I meant version 0.17.4 of the Solargraph gem. It only applies if you're using |
I updated |
Closing for issue cleanup. Apologies if this is still an issue. We are working to improve the core extension experience. |
Your environment
vscode-ruby
version: 0.15.0Make sure you have
ruby
,ruby-debug-ide
andruby-debug-basex19
installed before submitting your issue -- thank you !Expected behavior
Right-clicking or a class or method and selecting go to definition should direct me to the file where the definition exists.
CMD+ selecting a class, module or method should highlight and take you to the definition.
Actual behavior
After right-clicking and selecting go to definition, the definition is never found. You get a response saying "no definition found for... "
Hovering over a class, module or method and pressing down on CMD does not highlight the string and you are unable to select it trigger the go to definition.
Steps to reproduce the problem
Open any ruby file (*.rb) and find a method, module or class that you know is defined in another file and attempt to either right-click or CMD+click it and observe the actual behavior mentioned above
The text was updated successfully, but these errors were encountered: