Understanding Ace-Linters for LSP Event retrieval & sending raw events

[UnschooledGamer]

I'm trying to create an LSP Plugin API built around Ace-linters for Acode Editor, with the ability to send raw requests and listen to LSP Events, as well as other common LSP actions. Here's some initial code

I'd like any help given, as I felt overwhelmed looking at AceLanguageClient, ServiceManager, and LanguageProvider.

goals

• Listening to LSP Events.
• send raw requests.
• ability to use existing LSP workers/services with other LSP websocket-based LSP Servers.

[mkslanc]

Not sure, which help do you need, the discussion feels a bit abstract to me. But here some insights:

Key Components:

1. AceLanguageClient - Factory class that creates LanguageProvider instances
2. ServiceManager - Manages multiple LSP services, handles message routing
3. LanguageProvider - Main interface for Ace editor integration
4. LanguageClient - Handles individual LSP connections (WebSocket/WebWorker)

For raw requests (those which not implemented inside client) -> LanguageProvider.sendRequest should make it

You could use it with any websocket-based lsp-server, it doesn't matter a lot

[mkslanc]

Feel free to drop more detailed questions, if there are any

[UnschooledGamer]

Should LanguageProvider be instantiated once per Ace editor, or for every underlying LanguageClient instance? What is the recommended pattern if I need to support multiple LanguageClients?

Also, How do I listen and react to LSP events (like notifications or diagnostics) from LanguageClient/LanguageClients

[mkslanc]

LanguageProvider in most cases should be singleton, you just use registerEditor for each ace editor instance. If you could use webworker use it similar to this example. If you could only use main thread -> this multiple server example should direct you. Most events handled by client itself, but if you need to subscribe to some message you could use a bit hackish approach similar to this one

[UnschooledGamer]

If you need to subscribe to some message, you could use a bit hackish approach similar to this one

Hmm, I do think in future, it should expose the ability to listen to the Events sent by LSP instead of a hackish approach. AS some LSP servers may send custom events or notifications that a client might want to listen to.

Thanks for the Help, Marked the Discussion as Answered