You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A problem I had was that some references remained unresolved by the language server although they were correct.
The problem turned out to be that they were under a target directory, which is excluded by the language server, as seen in the following snippet.
I think ideally, the language server should do something more sensible than using the hardcoded exclusion rules and allow customization of that behaviour via options.
But for now, a workaround is to symlink the incorrectly excluded directories to a non-excluded name.
E.g. in my case I used ln -s target trgt.
The text was updated successfully, but these errors were encountered:
I agree, the current solution is not optimal and we should either query the build system (ideal) or at least the .gitignore as a heuristic on which files to exclude. Letting the user configure these exclusions manually could be convenient too. There's a todo comment a few lines above that addresses this:
A problem I had was that some references remained unresolved by the language server although they were correct.
The problem turned out to be that they were under a
target
directory, which is excluded by the language server, as seen in the following snippet.kotlin-language-server/shared/src/main/kotlin/org/javacs/kt/SourceExclusions.kt
Line 13 in bc53099
Solution
I think ideally, the language server should do something more sensible than using the hardcoded exclusion rules and allow customization of that behaviour via options.
But for now, a workaround is to symlink the incorrectly excluded directories to a non-excluded name.
E.g. in my case I used
ln -s target trgt
.The text was updated successfully, but these errors were encountered: