fwcd

> From my research it looks that the extension still does not support code from third party dependencies like JUnit or KMP. It should support that, but only if your...

``` Caused by: org.javacs.kt.util.KotlinLSException: No repositories found at $MAVEN_REPOSITORY, $MAVEN_HOME, $M2_HOME or $HOME/.m2` seems most relevant. ``` looks suspicious, the SLF4J stuff is fine (should probably add a troubleshooting entry...

I agree that it would be best to get rid of the warning, but ideally we should forward those messages to JUL too, so they get picked up by own...

Libraries often use SLF4J as their logging API

Note that Option+Scroll already does this.

These suggestions could also be factored out into a separate linting tool that `curry-language-server` then integrated (i.e. depends on).

The issue seems to be that the interface (`.icurry`) files seem to take precedence in the frontend if they already exist, otherwise the source file locations (e.g. `/lib/Prelude.curry`) are indexed...

A potential solution here would be to attach source information via `#line` directives in the `.icurry` files, similar to [those emitted by the C preprocessor](https://learn.microsoft.com/en-us/cpp/preprocessor/hash-line-directive-c-cpp?view=msvc-170#example). The frontend should also know...

The analysis API now contains a [platform interface](https://github.com/JetBrains/kotlin/blob/master/analysis/analysis-api-platform-interface/README.md), `KaSourceModificationService` might be what we are looking for.

Both syntax highlighting and code completion will be implemented in the Kotlin extension. See https://github.com/fwcd/kotlin-language-server/pull/157.