Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using the new Kotlin analysis API #25

Open
gAbelli opened this issue Jan 5, 2025 · 2 comments
Open

Investigate using the new Kotlin analysis API #25

gAbelli opened this issue Jan 5, 2025 · 2 comments

Comments

@gAbelli
Copy link

gAbelli commented Jan 5, 2025

The original repository has an open issue that mentions the possibility to use the analysis API to implement a language server for Kotlin: fwcd/kotlin-language-server#289.
I was wondering if this has been further investigated, or if there are plans to do so in the future.
Thanks for the great work by the way, it would be amazing to have a fully functional LSP for Kotlin!

@amgdev9
Copy link

amgdev9 commented Jan 5, 2025

A couple of months ago I did investigate the api to do incremental analysis, not working atm but I think this approach goes in the right direction. I share it in case someone wants to continue the research: fwcd/kotlin-analysis-server#1 (comment)

@gAbelli
Copy link
Author

gAbelli commented Jan 18, 2025

This thread in the Kotlin compiler Slack channel might be relevant.

The standalone part is still in the development state
https://kotlin.github.io/analysis-api/index_md.html#using-in-command-line-tools
It has been designed as an immutable view on the code, so it is not supposed to react on changes (at least yet)
The Standalone mode indeed doesn't support file mutation now.
Still, would you be able to provide your use-case? We are going to activate the Standalone platform development, so now we are interested in popular use-cases.

So it looks like the best we can do is letting JetBrains know that file mutation would be a useful feature for this use-case, and wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants