Question: Android Projects Support

[yamsergey]

It seems that current dependency resolver can't resolve all dependencies and sources for Android Project.

I want to create a wrapper which will generate workspace.json file with all the source sets and dependencies provided by Gradle plugins. But before I start, I would like to know:

• Is it a valid approach?
• Are there any plans to support Android Projects?
• Are there any options to use the LSP as Java/Kotlin library and call its APIs instead of creating additional proxy LSP server? Would be really nice option, since current Kotlin compiler API really hard to use due to lack of official documentation.

[zajac]

Hey!

• It is a totally valid approach to generate workspace.json
• the scope is so big, we still trying to plan our work and prioritise support for various kinds of projects, and tbh android is not yet in sight
• I didn't really get the third question. While it is certainly possible to use it as library, I would really like to know your use case, and what would you like to achieve? We don't have any documentation nor stable API atm

[yamsergey]

Fastest answer on the wild west :)

I want to make sort of extension for the LSP, let's say I want to add Colors Provider, but to do, so I need to know which value has been passed into Color class:

// Here it's quite easy to know the value by simply parsing the string
backgroundPrimary = Color(0xFFFFFFFF)

// But here I need to resolve variable value to know it
backgroundPrimary = Color(BACKGROUND_PRIMARY_COLOR)

Or find out if there is a certain implementation for an interface, or some annotations, etc., so I can suggest specific actions.

[zajac]

Right, now I see. Would the ability extend kotlin lsp with plugins solve this? We can kinda do both. We can provide with the library to build custom lsps, and we could provide extension API to extend the existing one. I think the latter is preferable because it allows to compose extensions and there is no need to restart lsp to add an extension

[yamsergey]

Both sounds awesome.

But let's say if I want to build an LSP which combines other LSPs (e.g. Flutter, which will involve Swift, Dart, Kotlin) then the ability to use the LSP as library might be more useful.

At the same time, extension might be easier to extend the functionality for only Kotlin based projects.

I can't decide, I would vote for either option 😂 But in any case it will take some time I guess.

[zajac]

Yeah, sure. Stay tuned! for now you may want to experiment with workspace.json