Closed tgodzik closed 5 years ago
Thank you for reporting! This is a SemanticDB bug, a test case reproducing the issue is already commited in the repo here https://github.com/scalameta/scalameta/blob/ff542e7c5b937822c12d0aa1ef7d6ab92b2fc5e1/tests/jvm/src/test/resources/example/Types.scala#L114
- obtained
+ expected
- final val clazzOf/*<=types.Test.Literal.clazzOf.*/ = classOf[Option[Int]]
+ final val clazzOf/*<=types.Test.Literal.clazzOf.*/ = classOf[Option/*=>scala.Option#*/[Int/*=>scala.Int#*/]]
Looks like there's nothing we can do on our side, this needs to be fixed upstream in the compiler. Definition used to work for classOf
in older versions of SemanticDB when we instrumented the typer but this was removed in https://github.com/scalameta/scalameta/pull/1804 to simplify compiler upgrades and improve interoperability with other compiler plugins.
Describe the bug Go to definition doesn't work when class is in classOf[]
To Reproduce Steps to reproduce the behavior:
Expected behavior Lsp would go to definition of the class inside classOf[]
Screenshots![bug](https://user-images.githubusercontent.com/3807253/56358079-d9210f80-61dd-11e9-9ce1-c7ed000918aa.png)
Installation:
Search terms goto definition classOf