31:00 the way the bqn_lsp project does docs is that it pulls down the BQN github and uses the markdown or generated html directly, to skip a step. So if you're building the extension, you could even go as far as versioning the LSP to support each build of BQN. edit: 40:00 oops lol
Yeah I misspoke it’s not really scraping in the usual sense. I wasn’t aware of bqn_lsp until now. Thats nice how it shows compiler errors inline. I wonder if my extension could use that / if it would make sense to combine them.
Great discussion!
31:00 the way the bqn_lsp project does docs is that it pulls down the BQN github and uses the markdown or generated html directly, to skip a step. So if you're building the extension, you could even go as far as versioning the LSP to support each build of BQN.
edit: 40:00 oops lol
Yeah I misspoke it’s not really scraping in the usual sense.
I wasn’t aware of bqn_lsp until now. Thats nice how it shows compiler errors inline. I wonder if my extension could use that / if it would make sense to combine them.
@@mitchellkember9291 I'm sorry, it was "bqnlsp" on sourcehut, no underscore!
We need an episode dedicated to Conor (and hosted by someone else)