Incorrect goto definition #4255
Assignees
Labels
improvement
Not a bug or a feature, but something general we can improve
semanticdb
Related to semanticdb usage in Metals
Milestone
Comments
|
Thanks for reporting! This seems another one that I ignored 😅 and it actually popped up a couple of times. Let me check it out. Keep those issues coming! :D |
tgodzik
added a commit
to tgodzik/metals
that referenced
this issue
Aug 24, 2022
Previously, DefinitionProvider would just look for the definition of object. Now, it also checks if the object is not a synthetic apply and in that case it tries to find that exact apply. Fixes scalameta#4255
tgodzik
added a commit
to tgodzik/metals
that referenced
this issue
Aug 24, 2022
Previously, DefinitionProvider would just look for the definition of object. Now, it also checks if the object is not a synthetic apply and in that case it tries to find that exact apply. Fixes scalameta#4255
tgodzik
added
improvement
|
Duplicate of #1809 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When doing a goto definition on
Indexerhere:metals/metals/src/main/scala/scala/meta/internal/metals/MetalsLanguageServer.scala
Line 2496 in ab314f8
This brings me to the companion object here:
metals/metals/src/main/scala/scala/meta/internal/metals/Indexer.scala
Line 610 in ab314f8
Even though in this scenario you'd expect and want it to bring you to the actual case class here:
metals/metals/src/main/scala/scala/meta/internal/metals/Indexer.scala
Line 46 in ab314f8
Expected behavior
I'd expect to navigate to the case class.
Operating system
macOS
Editor/Extension
Nvim (nvim-metals)
Version of Metals
0.11.8+11-bfe6c2ca-SNAPSHOT
Extra context or search terms
No response
The text was updated successfully, but these errors were encountered: