We wouldn't happen to have a BUILD LSP sitting aro...
# development
w
We wouldn't happen to have a BUILD LSP sitting around, would we? I'm experimenting with some neovim to see how much cooler it makes me, and an LSP would make my life mildly easier
b
That's what I worked on two years ago and lost to a rogue
rm -rf
TL;DR was "it's not hard to bootstrap one with pyright"
w
But not explicitly in vscode, right?
In short, I've been doing some stuff in the vscode plugin calling out to peek and a few other commands, and just a bunch of typescript shenanigans that are sorely misplaced.
b
I don't understand the question
w
Yeahhh, I was writing that as I was leaving the house - I have no idea what I was trying to ask
😂 2
c
@glamorous-tiger-7918 neovim!
w
All the cool kids are doing it, I just want to be popular
ðŸĪŠ 1
g
an LSP just for BUILD files feels like overkill 😛, we try to keep ours pretty slim. pyright using nvim-lspconfig isn't too bad. Only issue I had was with getting it to jive with our third party dependencies. I tried exporting a virtual environment using pants and pointing pyright at that but something was still off. At the moment I'm just dirtying my dev environment by pip installing where I run nvim. It's not "best practices" but it works for now...