rumno0

Thanks -

If its a straight error, then the error response is returned and we're all happy!

If the handler panics, the server crashes, so that's something I'm off to fix now!

Thanks!!!!

I've been thinking about this comment for a few hours now! I love it! I like building VS Code extensions and realized quickly the benefit of writing the logic in an LSP but I would never have thought to do the SSH config thing you describe.

I've now started a Makefile lsp since you've inspired me to think about the painful scenarios that LSP can solve if I think a bit wider.

Cheers for that!!

I actually started out using that. I wanted a debug UI to track messages which was the major driver in creating my own tbh

I disagree - you should have docstring and I don't think this is worse by having it... its just not ideal

I wrote this for the infracost LSP so I could write multiple IDE extensions. Its not even really a language server, its just a neat way to parse the Terraform/Cloudformation and return diagnostics.

Language servers are cool!

thanks!

Thankfully, I finally had a reason to build an LSP (infracost LSP), so it motivated this and I'm really pleased with it

Yeah some times godoc comments look crap by necessity

To a certain extent I agree - I've worked on projects where a resource amounts to a rounding error in the overall cloud bill; for many organizations, cost is an important NFR for a project.

Going off the other threads of this post, how much engineers should know or care about billing seems to be open for debate; I think an engineer needs to appreciate that often cost is one of the many trade-offs that need to be accounted for

Hey Itay, thanks, and thanks for commenting, great to hear from you!!