-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add: Workspace symbols #510
base: master
Are you sure you want to change the base?
Conversation
symbol) | ||
|
||
let workspace ~dir = | ||
let open FindFiles in |
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.
There are a bunch of places in the codebase with this kind of code.
Wondering if it's similar enough to grant some refactoring.
Or if the differences are too big to gain something.
E.g. the functionality to read sourceDirectories
could be factored out.
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.
Should we add a separate issue to track this @cristianoc ?
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 think this can be assessed now, and any follow-on work postponed.
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.
@aspeddro will you have a look at this? After that, this should be good for merging.
EDIT: Sorry, this + the other comments about the tests that @cristianoc had.
No tests for the new command yet right? |
export let runAnalysis = (args: Array<any>, binaryPath?: string, cwd?: string) => { | ||
let analysisPath = binaryPath != null ? binaryPath : getAnalysisBinaryPath() | ||
export let runAnalysis = (args: Array<any>, cwd?: string) => { | ||
let binaryPath = getAnalysisBinaryPath() |
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.
👍
@zth not necessarily about this PR, but we should consider beginning to add tests for the TypeScript part of the extension. That's where most breakages have been recently (and where we have no tests). |
Sounds good to me. Let's discuss this separately then. |
@@ -4,14 +4,14 @@ import * as v from "vscode-languageserver"; | |||
import * as rpc from "vscode-jsonrpc/node"; | |||
import * as path from "path"; | |||
import fs from "fs"; | |||
import os from "os"; |
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.
os
is not used
@@ -179,7 +188,7 @@ | |||
"vscode:prepublish": "npm run clean && npm run compile", | |||
"compile": "tsc -b", | |||
"watch": "tsc -b -w", | |||
"postinstall": "cd server && npm i && cd ../client && npm i && cd ../analysis/tests && npm i && cd ../reanalyze/examples/deadcode && npm i && cd ../termination && npm i" | |||
"postinstall": "cd server && npm i && cd ../client && npm i && cd ../analysis/reanalyze/examples/deadcode && npm i && cd ../termination && npm i" |
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.
Removed cd analysis/tests && npm i
. No longer has a package.json
file
There were the following changes in the tests folder:
|
181e056
to
b5c13b0
Compare
The last changes slowed down tests by about 3 seconds each clean build+test. |
Let me test something. |
Oops commit history is gone. |
This way we also avoid to merge conflict any other PR currently ongoing. |
Even if that count is inaccurate, we don't want those 3 seconds. |
Placing tests in When putting in |
Reading bsconfig is always tricky, as there are a bunch of rules, and might change in future. Related question: what about dependencies? About tests: there's quite a lot of freedom how test commands can be structured, and surely one can pass a folder as parameter or some other restriction to avoid noisy results. |
Making this run on CI: #519 |
Close #292