[FEATURE] Make an LSP for yuck

[Fejiberglibstein]

Description of the requested feature

Create a lsp for the yuck language. This lsp could have features such as

• autocomplete for widgets and widget's variables
• hover documentation for builtin widgets
• diagnostic messages for any errors
• goto definition for user-made widgets
• auto formatting

Proposed configuration syntax

No response

Additional context

I have made LSPs before in rust, so I would be willing to implement the lsp. I am just wondering if this is could be useful and something that people would be interested in.

[DOD-101]

I am currently looking into creating a formatter for yuck. This could, if I manage to get something decent production ready, be used in conjunction with the LSP. Then you wouldn't need to implement formatting in the LSP itself.

[elkowar]

A good LSP would definitely be a HUGE thing! If you wanna go for it, do it!

[Fejiberglibstein]

Sounds good, we'll see how far I get. I'll be finishing exams in 2 weeks so I won't get much done aside from using this to procrastinate until then.

Would the LSP be made as a separate executable run with something like eww-lsp, or would it be packaged along with the eww executable and run with something like eww start-lsp?

[Eugenenoble2005]

I've actually been hacking together something like that over the past few days.

2024-12-11.21-51-55.mp4

It's very basic and I've only managed to get simple context aware completions working. The problem is that it does not have any connection to the core rust code base so types are hard-coded and stuff according to the docs which is probably not the best way to achieve this.

[Fejiberglibstein]

Ah, very cool! My goal with this is to integrate it seamlessly into eww so that we could get stuff like diagnostics and go to definition without too much effort on my part. If you wanna help out with my implementation you can read everything I've mentioned so far in #1241. I'm still waiting on some feedback from @elkowar on how i should continue on my implementation.

[Eugenenoble2005]

Yh I have been reading your stuff. And it seems like a much better approach, I don't know rust(my impl is in c#) neither do I understand eww's codebase so I don't know how possible it is, but without some type of communication with eww, to achieve any form of reasonable diagnostics and code navigation I'd have to reimplement a yuck parser as closely as I can to @elkowar's implemetion which I imagine would be very difficult. Hopeful to see what you can come up with.

[Fejiberglibstein]

I don't know rust(my impl is in c#)

ah, well in that case I'd be welcome to any of your feedback/suggestions you might have.

I'd have to re-implement a yuck parser as closely as I can

yea doing that in a diff language and re-implementing it all yourself would be rather difficult

[Eugenenoble2005]

I don't know rust(my impl is in c#)

ah, well in that case I'd be welcome to any of your feedback/suggestions you might have.

I'd have to re-implement a yuck parser as closely as I can

yea doing that in a diff language and re-implementing it all yourself would be rather difficult

Yes it will be tricky.
My current implementation is located here in case you want to look at it.:
https://github.com/Eugenenoble2005/YuckLS/