This is the case where paths totally don't match and compiler panics and creates semanticdb next to the sources. Adding --semanticdb-sourceroot flag will cause it create it in the correct place for .scala files.
However, we don't actually use semanticdb for single files anyway, since the paths will still be broken for scripts. Maybe instead of --semanticdb-sourceroot, we could have a flag that stops semanticdb from being produced all together?
CC: @tgodzik @Gedochao
resolves: https://github.com/scalameta/metals/issues/6508
This is the case where paths totally don't match and compiler panics and creates
semanticdb
next to the sources. Adding--semanticdb-sourceroot
flag will cause it create it in the correct place for.scala
files.However, we don't actually use semanticdb for single files anyway, since the paths will still be broken for scripts. Maybe instead of
--semanticdb-sourceroot
, we could have a flag that stops semanticdb from being produced all together? CC: @tgodzik @Gedochao