lapce-plugin-rust
lapce-plugin-rust copied to clipboard
lapce
It would be good to have the ability to send asynchronous requests, and handle the result via a callback. Ex: Sending a command to a spawned LSP server shouldn't typically...
Currently `LapcePlugin` is defined as: ```rust #[allow(unused_variables)] pub trait LapcePlugin { fn handle_request(&mut self, id: u64, method: String, params: Value) {} fn handle_notification(&mut self, method: String, params: Value) {} }...
There's various pieces of the API that should probably be hidden or made non-constructable. Hiding functions would allow us to later replace or alter the code behind them without breaking...
I'm writing a plugin for php, but it doesn't work. The only feedback I got from the console was `parse error expected value at line 1 column 1` Is there...
Currently, one can respond to a request (received in `handle_request`) by using `object_to_stdout`, but that is a poor API. Here's my idea of the function definition for responding: ```rust ///...
A nice way, like #8, for sending requests is desirable. However, we run into the issue that the plugin author needs to handle any responses from the editor that they...
There should be a function to easily send a notification to the client from a plugin. This can currently be achieved via `object_to_stdout`, but in a somewhat unpleasant manner and...
Related: https://github.com/lapce/lapce/pull/579
I participated in the internal test of a brand new language. I want to adapt lapce for this language. How should I add syntax highlighting and access the lsp of...
I have a workspace with ~30 crates in it; `cargo check` can sometimes take quite a while. So, doing an edit and then attempting to build in a shell often...
