-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: add sqruff as a VSCode extension #369
Conversation
Benchmark for 8b0ce87Click to view benchmark
|
Benchmark for a07c3efClick to view benchmark
|
9276efa
to
631b9e6
Compare
Benchmark for fbe7902Click to view benchmark
|
Benchmark for b1ae0cdClick to view benchmark
|
Benchmark for cc1d967Click to view benchmark
|
…refactor diagnostic checking
Benchmark for b8cbdd2Click to view benchmark
|
Benchmark for c89602fClick to view benchmark
|
Benchmark for 6e0da46Click to view benchmark
|
Benchmark for da250beClick to view benchmark
|
Benchmark for 14206c7Click to view benchmark
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @gvozdvmozgu,
Great work, I am just wondering, I am struggling to get it to work in browser, what are the steps that you have run to test/run it?
export function activate(context: vscode.ExtensionContext) { | ||
const serverMain = vscode.Uri.joinPath( | ||
context.extensionUri, | ||
"dist/browserServerMain.js", | ||
); | ||
|
||
const worker = new Worker(serverMain.toString(true)); | ||
worker.onmessage = (message) => { | ||
if (message.data !== "OK") { | ||
return; | ||
} | ||
|
||
const cl = new LanguageClient("sqruff-lsp", "Sqruff LSP", { documentSelector: [{ language: "sql" }] }, worker); | ||
cl.start().then(() => { }); | ||
}; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am struggling to see how you are testing this in the browser. Did you run npm run run-in-browser
? and what before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm run build:wasm_lsp && npm run compile && npm run run-in-browser
@@ -0,0 +1,17 @@ | |||
{ | |||
"compilerOptions": { | |||
"module": "Node16", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: This here feels slightly odd version but not important.
with: | ||
push_options: '--force' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we should add some CI checks for this as well.
Benchmark for 36de1b5Click to view benchmark
|
Benchmark for bde5b91Click to view benchmark
|
I think there are a few things we should improve, but in the meantime, we should merge this:
|
No description provided.