LSP Backend

[FastestMolasses]

Description

Contains the LSP backend.

Related Issues

Checklist

• I read and understood the contributing guide as well as the code of conduct
• The issues this PR addresses are related to each other
• My changes generate no new warnings
• My code builds and runs on my machine
• My changes are all related to the related issue above
• I documented my code

[matthijseikelenboom]

Looks good man. I've left some notes on things that have to change and some that should be discussed

[tom-ludwig]

Great work! I'm really excited about getting all this functionality fully implemented. I found just a few small issues. We're still missing tests, and I'm not sure how to mock good responses from the language server or set one up for testing from scratch. Also, could you rename the folder LanguageServer+ to something like LanguageServerExtensions?

[FastestMolasses]

I'll take a look at adding a mock provider for tests

[FastestMolasses]

So I think one way we could do it is by creating a fake server binary. It would be a swift script that gets compiled and it would send back a randomized json response based on the request it received. Can I get some thoughts on this before I proceed with it? It would be a big task to get a mock language server that can effectively test the implementation. @CodeEditApp/maintainers

[tom-ludwig]

No, that would be a waste of time right now. Tests are crucial in CE to ensure everything works now and after others make changes, especially with tightly coupled code that many people use and modify. But we’re not even using your language server functions yet. If setting up tests for server binaries is too complicated or time-consuming, I'd say skip them for now. We definitely need to create them eventually😅

[FastestMolasses]

Ok I'll make an issue for it and I can do it in the next milestone.

[matthijseikelenboom]

I see it's already merged, but still one point. (Didn't have to be done in this PR tho)

[matthijseikelenboom]

In the future we need to do something with this. CacheKey is now a callable struct from within the entire project, but it doesn't describe what it does at all.

Either should be fixed by moving to modules or very explicit documentation

[FastestMolasses]

I'll make the naming more clear in my next or