aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
...
* Make inlay hints colors more configurableVeetaha2020-08-262-49/+93
|
* Merge #5841bors[bot]2020-08-241-0/+8
|\ | | | | | | | | | | | | | | | | | | 5841: Gate stream.pipeline workaround on fixed versions of node r=matklad a=Veetaha Fixes the symptom of https://github.com/cdr/code-server/issues/1810 Original report here: https://github.com/rust-analyzer/rust-analyzer/issues/3167#issuecomment-678390564 Thanks to @hjfreyer for precise investigation :D Co-authored-by: Veetaha <[email protected]>
| * Gate stream.pipeline workaround on fixed versions of nodeVeetaha2020-08-211-0/+8
| |
* | Dont ask me why...Veetaha2020-08-211-1/+0
|/
* Align diagnostics config with the rest of rust-analyzerAleksey Kladov2020-08-181-6/+6
|
* Merge #5682bors[bot]2020-08-181-0/+9
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 5682: Add an option to disable diagnostics r=matklad a=popzxc As far as I know, currently it's not possible to disable a selected type of diagnostics provided by `rust-analyzer`. This causes an inconvenient situation with a false-positive warnings: you either have to disable all the diagnostics, or you have to ignore these warnings. There are some open issues related to this problem, e.g.: https://github.com/rust-analyzer/rust-analyzer/issues/5412, https://github.com/rust-analyzer/rust-analyzer/issues/5502 This PR attempts to make it possible to selectively disable some diagnostics on per-project basis. Co-authored-by: Igor Aleksanov <[email protected]>
| * Merge branch 'master' into add-disable-diagnosticsIgor Aleksanov2020-08-141-2/+2
| |\
| * | Restore final newline in package.jsonIgor Aleksanov2020-08-131-1/+1
| | |
| * | Merge branch 'master' into add-disable-diagnosticsIgor Aleksanov2020-08-123-12/+6
| |\ \
| * | | Add a configuration option for the vscode extensionIgor Aleksanov2020-08-121-1/+10
| | | |
| | | |
| \ \ \
*-. \ \ \ Merge #5776 #5780bors[bot]2020-08-171-0/+3
|\ \ \ \ \ | | | |_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5776: Fix eslint errors on .eslintrc.js and rollup.config.js r=matklad a=fuafa Eslint complains if these two files does not include in the `tsconfig.json`. ``` Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser. The file does not match your project config: .eslintrc.js. The file must be included in at least one of the projects provided.eslint ``` ![image](https://user-images.githubusercontent.com/20750310/90338269-176d4f80-e01b-11ea-8710-3ea817b235d2.png) 5780: Fixup whitespace when adding missing impl items r=matklad a=jDomantas Generate properly formatted whitespace when adding impl items - with an empty line between items and removing extra whitespace that often appears at the end. This is my first time working on rust analyzer so I'm not very familiar with its internal APIs. If there's a better way to do such syntax tree editing I'd be glad to hear it. Co-authored-by: xiaofa <[email protected]> Co-authored-by: jDomantas <[email protected]>
| * / | | Fix eslint errors on .eslintrc.js and rollup.config.jsxiaofa2020-08-161-0/+3
| |/ / /
* | | | Merge #5782bors[bot]2020-08-172-2/+5
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5782: Fix StatusNotification r=matklad a=vsrs This PR fixes the following: As per specification `params` property in [NotificationMessage ](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#notificationMessage) should be `array | object` while RA uses `"loading" | "ready" | "invalid" | "needsReload"`. Co-authored-by: vsrs <[email protected]>
| * | | Fix StatusNotificationvsrs2020-08-172-2/+5
| | |/ | |/|
* / | Rename ra_toolchain -> toolchainAleksey Kladov2020-08-121-2/+2
|/ /
* | Merge #5697bors[bot]2020-08-101-8/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 5697: Remove workaround for semantic token flickering r=jonas-schievink a=kjeremy See: https://github.com/microsoft/vscode-languageserver-node/issues/576#issuecomment-593384479 This has been fixed since vscode 1.44 Co-authored-by: Jeremy Kolb <[email protected]>
| * | Remove 'as any'Jeremy Kolb2020-08-091-1/+1
| | |
| * | Remove workaround for semantic token flickeringJeremy Kolb2020-08-091-7/+1
| | | | | | | | | | | | | | | | | | See: https://github.com/microsoft/vscode-languageserver-node/issues/576#issuecomment-593384479 This has been fixed since vscode 1.44
* | | 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 typo in settings descriptionRüdiger Herrmann2020-08-081-1/+1
|/ | | Remove a duplicate word from the description of the `warningsAsHint` setting.
* Merge #5513bors[bot]2020-07-311-2/+10
|\ | | | | | | | | | | | | | | | | | | 5513: Try figure out correct workspace in vscode multi root workspace r=vsrs a=urbandove the code to replace the root with the `${workspaceRoot}` arg breaks in multi root workspaces as it needs a qualifier `${workspaceRoot:workspaceName}` This PR attempts to figure out the root workspace - and if it cant find it falls back to the first workspace Co-authored-by: Urban Dove <[email protected]>
| * delete empty lineUrban Dove2020-07-261-1/+0
| |
| * try select correct workspace in vscode multi workspaceUrban Dove2020-07-261-2/+11
| |
* | flycheck: Added checkOnSave.noDefaultFeaturesClemens Wasser2020-07-301-0/+8
| | | | | | | | | | | | This commit adds the option `rust-analyzer.checkOnSave.noDefaultFeatures` and fixes #5550.
* | SSR: Restrict to current selection if anyDavid Lattimore2020-07-292-2/+4
| | | | | | | | | | The selection is also used to avoid unnecessary work, but only to the file level. Further restricting unnecessary work is left for later.
* | Add toggle for experimental diagnosticsJonas Schievink2020-07-241-5/+10
| |
* | SSR: Fix a typescript lint warningDavid Lattimore2020-07-241-1/+1
| |
* | SSR: Pass current file position through to SSR code.David Lattimore2020-07-242-3/+13
|/ | | | In a subsequent commit, it will be used for resolving paths.
* Merge #5480bors[bot]2020-07-231-0/+4
|\ | | | | | | | | | | | | | | | | | | | | 5480: Fix snippetTextEdits applying to other files r=matklad a=TimoFreiberg Fixes #4551 `vscode.window.visibleTextEditors` only contains editors whose contents are being displayed at the moment, so the previous logic only worked if the other file for which a snippetTextEdit is being received was visible in a separate split. I feel that this is a hacky approach, so feel free to reject it for something nicer :) Co-authored-by: Timo Freiberg <[email protected]>
| * Fix snippetTextEdits applying to other filesTimo Freiberg2020-07-221-0/+4
| | | | | | | | | | | | | | vscode.window.visibleTextEditors only contains editors whose contents are being displayed at the moment, so the previous logic only worked if the other file for which a snippetTextEdit is being received was visible in a separate split.
* | ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's ↵James Leitch2020-07-232-3/+10
|/ | | | owner and source. VSCode LSP updated to specify owner.
* Bump lodash from 4.17.15 to 4.17.19 in /editors/codedependabot[bot]2020-07-161-3/+3
| | | | | | | Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19) Signed-off-by: dependabot[bot] <[email protected]>
* Automatically reload project info on Cargo.toml changesAleksey Kladov2020-07-101-0/+5
|
* Workaround rollup messing up default importsVeetaha2020-07-081-1/+4
|
* Gzip artifactsVeetaha2020-07-072-16/+17
| | | | | | | | | | Co-authored-by: bjorn3 <[email protected]> Override miniz_oxide to build it with optimizations Building this crate with optimizations decreases the gzipping part of `cargo xtask dist` from `30-40s` down to `3s`, the overhead for `rustc` to apply optimizations is miserable on this background
* Add a command to compute memory usage statisticsJonas Schievink2020-07-074-0/+44
|
*---. Merge #5235 #5236 #5241bors[bot]2020-07-072-4/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5235: Don't ping people in PRs r=matklad a=lnicola 5236: Disable ES module interop r=matklad a=lnicola 5241: Clippy perf warnings r=matklad a=kjeremy Removes redundant clones Co-authored-by: Laurențiu Nicola <[email protected]> Co-authored-by: Aleksey Kladov <[email protected]> Co-authored-by: kjeremy <[email protected]>
| | * | Disable ES module interopLaurențiu Nicola2020-07-062-4/+2
| | |/
* | / Consider EPERM error as other vscode processes using rust-analyzerVeetaha2020-07-071-1/+1
| |/ |/|
* | Fix: allow for binaries from $PATH to pass validity checkVeetaha2020-07-061-6/+2
|/
* Revert "Dispose logger on extension deactivation"Veetaha2020-07-052-6/+0
| | | | | This reverts commit 13872543e074adc153b440660beda441fd562f53. That commit was wrong because we use-after-free the logger
* Dispose logger on extension deactivationVeetaha2020-07-052-0/+6
|
* Improve client logging (use output channel and more log levels)Veetaha2020-07-054-18/+49
|
* Merge #5203bors[bot]2020-07-031-1/+1
|\ | | | | | | | | | | | | | | 5203: Fix typo in description of vscode setting r=matklad a=Nashenas88 Co-authored-by: Paul Daniel Faria <[email protected]>
| * Fix typo in description of vscode settingPaul Daniel Faria2020-07-031-1/+1
| |
* | Merge #5202bors[bot]2020-07-035-13/+191
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5202: Runnable env r=matklad a=vsrs This PR adds on option to specify (in the settings.json) environment variables passed to the runnable. The simplest way for all runnables in a bunch: ```jsonc "rust-analyzer.runnableEnv": { "RUN_SLOW_TESTS": "1" } ``` Or it is possible to specify vars more granularly: ```jsonc "rust-analyzer.runnableEnv": [ { // "mask": null, // null mask means that this rule will be applied for all runnables env: { "APP_ID": "1", "APP_DATA": "asdf" } }, { "mask": "test_name", "env": { "APP_ID": "2", // overwrites only APP_ID } } ] ``` You can use any valid RegExp as a mask. Also note that a full runnable name is something like *run bin_or_example_name*, *test some::mod::test_name* or *test-mod some::mod*, so it is possible to distinguish binaries, single tests, and test modules with this masks: `"^run"`, `"^test "` (the trailing space matters!), and `"^test-mod"` respectively. Fixes #4450 I suppose this info should be somewhere in the docs, but unsure where is the best place. Co-authored-by: vsrs <[email protected]>
| * Fix workspaceRootvsrs2020-07-031-1/+3
| |
| * code lintingvsrs2020-07-033-32/+32
| |
| * Add testsvsrs2020-07-034-10/+128
| |
| * Add runnable env support.vsrs2020-07-034-11/+69
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 16:25:24 +0000