aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/util.ts
Commit message (Collapse)AuthorAgeFilesLines
* Dont ask me why...Veetaha2020-08-211-1/+0
|
* Fix no inlay hints / unresolved tokens until manual editVeetaha2020-08-081-3/+3
| | | | | | | | | | No we return ContentModified during the workspace loading. This signifies the language client to retry the operation (i.e. the client will continue polling the server while it returns ContentModified). I believe that there might be cases of overly big projects where the backoff logic we have setup in `sendRequestWithRetry` (which we use for inlay hints) might bail too early (currently the largest retry standby time is 10 seconds). However, I've tried on one of my project with 500+ dependencies and it is still enough.
* Fix: allow for binaries from $PATH to pass validity checkVeetaha2020-07-061-6/+2
|
* Revert "Dispose logger on extension deactivation"Veetaha2020-07-051-4/+0
| | | | | This reverts commit 13872543e074adc153b440660beda441fd562f53. That commit was wrong because we use-after-free the logger
* Dispose logger on extension deactivationVeetaha2020-07-051-0/+4
|
* Improve client logging (use output channel and more log levels)Veetaha2020-07-051-10/+41
|
* Never disable error logging on the frontendVeetaha2020-06-221-1/+0
|
* Change Runnable.bin -> Runnable.kindveetaha2020-05-311-0/+18
| | | | | | As per matklad, we now pass the responsibility for finding the binary to the frontend. Also, added caching for finding the binary path to reduce the amount of filesystem interactions.
* Add `inRustProject` when-clause for commands.vsrs2020-05-271-0/+5
|
* Partially fix displaying inlay hints in Github PR diff viewsveetaha2020-05-261-4/+5
|
* Fix cargo not found on macos bug at vscode extension sideveetaha2020-05-061-0/+11
|
* vscode: add syntax tree inspection hovers and highlightsveetaha2020-03-311-2/+2
|
* Rewrite auto-updateAleksey Kladov2020-03-191-54/+0
| | | | | | | | | | | | | | Everything now happens in main.ts, in the bootstrap family of functions. The current flow is: * check everything only on extension installation. * if the user is on nightly channel, try to download the nightly extension and reload. * when we install nightly extension, we persist its release id, so that we can check if the current release is different. * if server binary was not downloaded by the current version of the extension, redownload it (we persist the version of ext that downloaded the server).
* vscode-prerefactor: add some utility functionsVeetaha2020-03-141-6/+63
|
* vscode: prerefactor util.ts and ctx.tsVeetaha2020-03-071-3/+9
|
* Centralize the check for languageId on documentJulien Roncaglia2020-03-021-0/+8
| | | | Also move visibleRustEditors to Ctx
* vscode: simplify assert.eq() to assert() as per matkladVeetaha2020-02-281-11/+1
|
* vscode: add dat semicolonVeetaha2020-02-281-1/+1
|
* vscode: add equality assertionVeetaha2020-02-281-0/+10
|
* vscode: rename nodeAssert -> nativeAssertVeetaha2020-02-281-2/+2
|
* vscode: add error loging on failed assertionVeetaha2020-02-281-1/+6
|
* vscode: migrate to more type-safe assert implVeetaha2020-02-281-4/+8
|
* vscode: migrate inlay_hints to rust-analyzer-api.tsVeetaha2020-02-241-8/+8
|
* vscode: gracefully handle cancellation errorsVeetaha2020-02-231-0/+40
|
* Extract client-side loggingAleksey Kladov2020-02-221-0/+18