-
Notifications
You must be signed in to change notification settings - Fork 0
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
Extension unable to connect #13
Comments
Sorry for taking so long. Yes, the error is because there is no idle object in options, which inherits from The Lapce proxy is a bit confusing to understand, but I'll try to be as simple as possible. Suppose you install an extension, its parameters are intact, i.e. its configuration, how does the Lapce proxy send to the extension those parameters? Through an object, but here comes its particularity, it only sends the properties that have been manipulated at least once. You get the idea, when you install a new extension, you have never manipulated its parameters, so, guess how Lapce sends the object? Exactly, empty. That's when the code goes into chaos. Obviously, as we had been testing several configurations, the object that Lapce sent us was complete, with each of the parameters, so we didn't have that inconvenience. If you iterate all the configuration parameters the extension will work. But of course, we understand that this is annoying and we will be working on a solution. Thanks again! |
Additionally, I am aware of your proposal. From what I understood, you suggested that the lapcord binaries (lsp) be located in the |
The suggestion i proposed eliminates the use of installing lapcord binary provided |
Despite Lapcord installed globally, the extension is unable to connect. Below is the screenshot of the log file. I am currently on POP OS 22.04.
The text was updated successfully, but these errors were encountered: