aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
...
| * vscode: npm run fixVeetaha2020-03-142-4/+4
| |
| * vscode: amend server installation logic to account for nightliesVeetaha2020-03-143-52/+57
| |
| * vscode: add nightly extension installation logicVeetaha2020-03-141-0/+131
| |
| * vscode: prepare config for nightliesVeetaha2020-03-141-15/+96
| |
| * vscode: get release date from release infoVeetaha2020-03-142-14/+7
| |
| * vscode-prerefactor: add some utility functionsVeetaha2020-03-141-6/+63
| |
| * vscode-prerefactor: merge two files into downloads.tsVeetaha2020-03-142-50/+46
| |
* | Merge #3540bors[bot]2020-03-162-8/+11
|\ \ | | | | | | | | | | | | | | | | | | | | | 3540: Swtches to rust SSR query check r=matklad a=mikhail-m1 related to #3186 Co-authored-by: Mikhail Modin <[email protected]>
| * | Swtches to rust SSR query checkMikhail Modin2020-03-152-8/+11
| | |
* | | Merge #3561 #3577bors[bot]2020-03-134-3/+24
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3561: feat: add debug code lens r=matklad a=hdevalke Refs #3539 3577: Protect against infinite macro expansion in def collector r=edwin0cheng a=flodiebold Something I noticed while trying to make macro expansion more resilient against errors. There was a test for this, but it wasn't actually working because the first recursive expansion failed. (The comma...) Even with this limit, that test (when fixed) still takes some time to pass because of the exponential growth of the expansions, so I disabled it and added a different one without growth. CC @edwin0cheng Co-authored-by: Hannes De Valkeneer <[email protected]> Co-authored-by: hdevalke <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
| * | Update editors/code/src/config.tshdevalke2020-03-121-1/+0
| | | | | | | | | Co-Authored-By: Veetaha <[email protected]>
| * | fixup! feat: add debug code lensHannes De Valkeneer2020-03-122-0/+2
| | | | | | | | | | | | autodetect vscode-lldb
| * | fixup! feat: add debug code lensHannes De Valkeneer2020-03-121-6/+1
| | | | | | | | | | | | avoid repetition of `--no-run`
| * | fixup! feat: add debug code lensHannes De Valkeneer2020-03-121-2/+1
| | |
| * | feat: add debug code lensHannes De Valkeneer2020-03-113-3/+29
| | | | | | | | | | | | Refs #3539
* | | Simpler deserializationAleksey Kladov2020-03-121-1/+6
| | |
* | | Merge #3543bors[bot]2020-03-123-5/+17
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3543: Parameter inlay hint separate from variable type inlay? #2876 r=matklad a=slyngbaek Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side Co-authored-by: Steffen Lyngbaek <[email protected]>
| * | Make maxLength nullable againSteffen Lyngbaek2020-03-121-2/+2
| | |
| * | Switch from Vec<InlayKind> to object with propsSteffen Lyngbaek2020-03-123-8/+9
| | | | | | | | | | | | | | | | | | | | | - Instead of a single object type, use several individual nested types to allow toggling from the settings GUI - Remove unused struct definitions - Install and test that the toggles work
| * | Address Issues from GithubSteffen Lyngbaek2020-03-101-1/+3
| | | | | | | | | | | | | | | | | | | | | - Updated naming of config - Define struct in ra_ide and use remote derive in rust-analyzer/config - Make inlayConfig type more flexible to support more future types - Remove constructor only used in tests
| * | Parameter inlay hint separate from variable type inlay? #2876Steffen Lyngbaek2020-03-103-4/+13
| |/ | | | | | | | | | | | | | | | | Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side
* / Add additional_outdirs in configEdwin Cheng2020-03-102-0/+2
|/
* vscode: groupd updates-related config under `updates` section as per @matkladVeetaha2020-03-091-1/+1
|
* vscode: fix inversion of askBeforeDownloadVeetaha2020-03-081-1/+1
|
* vscode: rename alwaysDownloadServer -> askBeforeDownloadVeetaha2020-03-081-1/+1
| | | | | | | | | | | The new name seems much simpler and it doesn't limit this config value only to downloading the server binary. Thus we wouldn't need to create another config properties to handle other downloads whatsoever. Anyway, I believe (heuristically) that most of the users would want to set "askBeforeDownload": false once and never bother clicking on the notification again (because otherwise there is no big point in installing rust-analyzer if it cannot install the server)
* vscode: care about alwaysDownloadServer option before askingVeetaha2020-03-073-23/+31
| | | | | | | Also renamed BinarySource to ArtifactSource in anticipation of nightlies installation that requires downloading not a binary itself but .vsix package, thus generalized to `artifact` term
* vscode: post refactor HintsUpdater (simplify create() -> constructor call)Veetaha2020-03-071-16/+10
|
* vscode: more privacy for HintsUpdaterVeetaha2020-03-071-1/+1
|
* vscode: remove logging from inlays, run fix lint issuesVeetaha2020-03-071-18/+7
|
* vscode: remove logic for caching editors as per @matkladVeetaha2020-03-071-222/+136
|
* vscode: prerefactor util.ts and ctx.tsVeetaha2020-03-072-10/+14
|
* vscode: refresh all editors on text changes, simplify inlays apiVeetaha2020-03-071-13/+11
|
* vscode: add dat semicolonVeetaha2020-03-071-1/+1
|
* vscode: simpifyVeetaha2020-03-071-5/+1
|
* vscode: redesign inlay hints to be capable of handling multiple editorsVeetaha2020-03-072-106/+273
|
* vscode: extract Type and Param hint cases of InlayHint at type level (needed ↵Veetaha2020-03-071-8/+14
| | | | further)
* Merge #3388bors[bot]2020-03-035-15/+25
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3388: Remove inlay hint in diff views r=matklad a=vbfox If the left side of a diff view that contain the old version of the file apply inlays they are misplaced and produce a weird display: ![image](https://user-images.githubusercontent.com/131878/75628802-b1ac1900-5bdc-11ea-8c26-6722d8e38371.png) After the change: ![image](https://user-images.githubusercontent.com/131878/75628831-e91ac580-5bdc-11ea-9039-c6b4ffbdb2be.png) The detection is done by blacklisting the url schemes used by git and subversion scm extensions, whitelisting `file` is also possible but neither is perfect as VSCode now support both pluggable scm extensions and pluggable remote filesystems. But I suspect that the list of scm extensions is more easily manageable. **Note**: I can rebase on #3378 if needed as it touches the same lines of code Co-authored-by: Julien Roncaglia <[email protected]>
| * Centralize the check for languageId on documentJulien Roncaglia2020-03-025-24/+25
| | | | | | | | Also move visibleRustEditors to Ctx
| * Remove inlay in diff viewsJulien Roncaglia2020-03-011-1/+10
| | | | | | | | | | | | | | | | If the left side of a diff view that contain the old version of the file apply inlays they are misplaced. The detection is done by blacklisting the url schemes used by git and subversion scm extensions.
* | Don't fail loudly if the old highlighting breaksAleksey Kladov2020-03-021-4/+6
|/
* vscode: simplify assert.eq() to assert() as per matkladVeetaha2020-02-282-15/+4
|
* vscode: add dat semicolonVeetaha2020-02-281-1/+1
|
* vscode: add equality assertionVeetaha2020-02-282-2/+12
|
* 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-283-8/+10
|
* Reset fontStyle for inlay hintsAleksey Kladov2020-02-281-0/+2
| | | | Otherwise, we get bold hints on `true` and `false`
* Fix lintAleksey Kladov2020-02-271-1/+1
|
* Fix flickering with new syntax highlightingAleksey Kladov2020-02-271-1/+9
|
* Config to switch to semantic tokensAleksey Kladov2020-02-263-3/+10
|