aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge #3514bors[bot]2020-03-091-0/+5
|\ | | | | | | | | | | | | | | | | | | | | | | 3514: vscode: askBeforeDownload option r=matklad a=Veetaha This is a small step towards #3402, also implements my proposal stated in #3403 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. @matklad @lnicola Co-authored-by: Veetaha <[email protected]>
| * vscode: groupd updates-related config under `updates` section as per @matkladVeetaha2020-03-091-1/+1
| |
| * vscode: rename alwaysDownloadServer -> askBeforeDownloadVeetaha2020-03-081-3/+3
| | | | | | | | | | | | | | | | | | | | | | 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: contribute "alwaysDownloadServer" option to configVeetaha2020-03-071-0/+5
| |
* | Use markdown description in vscodeJulien Roncaglia2020-03-081-9/+9
|/
* :arrow_up: npm depsAleksey Kladov2020-03-061-1/+1
|
* Don't creat public APIs with typosAleksey Kladov2020-03-061-1/+1
|
* Concise mode for parameter hintsAleksey Kladov2020-03-061-0/+4
| | | | | This works around VS Code bug where it tries to cram everything in a tiny popup, and brings experience closer to Intellij.
* Feature flag for arg snippetsAleksey Kladov2020-03-061-0/+4
|
* Update code dependenciesJeremy Kolb2020-03-031-9/+9
|
* Minimal viable metaAleksey Kladov2020-03-021-1/+6
|
* Fix union classificationAleksey Kladov2020-02-281-2/+0
|
* Merge #3363bors[bot]2020-02-281-20/+64
|\ | | | | | | | | | | | | | | | | | | | | 3363: Cleanup highlighting tags r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Cleanup highlighting tagsAleksey Kladov2020-02-281-17/+70
| |
| * add more tagsAleksey Kladov2020-02-281-9/+0
| |
* | removing ctrl+r key binding fixes #2733Jason Williams2020-02-281-5/+0
| |
* | vscode: added feature flags for better short-term uxVeetaha2020-02-271-1/+23
|/
* Map builtinAleksey Kladov2020-02-271-0/+6
|
* Set attr scopeAleksey Kladov2020-02-271-0/+6
|
* Map unsafe keywordAleksey Kladov2020-02-271-0/+6
|
* Fix styleAleksey Kladov2020-02-271-1/+1
|
* Actually gate CI on eslintAleksey Kladov2020-02-271-1/+2
|
* Merge #3308bors[bot]2020-02-271-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3308: vscode: fix vscode-vim keybindings conflict r=matklad a=Veetaha Closes #3013 I hope vscode-vim extension overrides the `type` command so that it prevents some keypresses to reach the text document editor. It conflicts with our `onEnter` keybinding that is used to support automatic doc comments extending and indentation insertion. The VSCode-native way to implement this would be to use regular expressions, but as per matklad it is considered not acceptable for the language server. Thus we implement it via a `Enter` keybinding that invokes our `onEnter` command which does it via the language-server. At the end of the day we may only apply ad hoc workarounds for conflicting extensions. But vscode has another bug for that. You either cannot use parantheses in `when` condition of a keybinding or it just malfunctions. See an issue about that here: https://github.com/microsoft/vscode/issues/91473 To get the ultimate context, follow this [zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Enhanced.20typing) Co-authored-by: Veetaha <[email protected]>
| * vscode: fix vscode-vim keybindings conflictVeetaha2020-02-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vscode-vim extension overrides the `type` command so that it prevents some keypresses to reach the text document editor. It conflicts with our `onEnter` keybinding that is used to support automatic doc comments extending and indentation insertion. The VSCode-native way to implement this would be to use regular expressions, but as per matklad it is considered not acceptable for the language server. Thus we implement it via a `Enter` keybinding that invokes our `onEnter` command which sends a request to rust-analyzer process and applies the appropriate source change recieved from it. At the end of the day we may only apply ad hoc workarounds for conflicting extensions. But vscode has another bug for that. You either cannot use parantheses in `when` condition of a keybinding or it just malfunctions. See an issue about that here: https://github.com/microsoft/vscode/issues/91473 To get the ultimate context, follow this zulip thread: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Enhanced.20typing
* | Color constantsAleksey Kladov2020-02-271-0/+9
| |
* | Better highlightign APIAleksey Kladov2020-02-271-0/+19
| |
* | wipAleksey Kladov2020-02-261-0/+14
| |
* | Config to switch to semantic tokensAleksey Kladov2020-02-261-0/+5
| |
* | Merge pull request #3321 from kjeremy/semantic-clientAleksey Kladov2020-02-261-0/+1
|\ \ | | | | | | Enable SemanticTokens on the client
| * | Enable SemanticTokens on the clientJeremy Kolb2020-02-261-0/+1
| |/ | | | | | | This will crash the extension on stable and insiders without the "--enable-proposed-api matklad.rust-analyzer" command line switch.
* / Remove unnecessary depAleksey Kladov2020-02-261-2/+0
|/
* vscode: bump TypeScript versionVeetaha2020-02-241-1/+1
|
* Extract client-side loggingAleksey Kladov2020-02-221-0/+5
|
* Improve server version infoEdwin Cheng2020-02-211-0/+5
|
* Rename config value for server PathAleksey Kladov2020-02-181-1/+1
|
* Rename the binary to rust-analyzerAleksey Kladov2020-02-181-2/+2
|
* Merge pull request #3209 from matklad/eslintAleksey Kladov2020-02-181-2/+4
|\ | | | | Eslint
| * Migrate to eslintAleksey Kladov2020-02-171-2/+4
| |
* | vscode-languageclient 6.1.1kjeremy2020-02-171-1/+1
|/
* Fix extension nameAleksey Kladov2020-02-171-1/+1
|
* Merge #3187bors[bot]2020-02-171-2/+2
|\ | | | | | | | | | | | | | | 3187: :arrow_up: npm deps r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * :arrow_up: npm depsAleksey Kladov2020-02-171-2/+2
| |
* | Merge #3099bors[bot]2020-02-171-0/+5
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | 3099: Init implementation of structural search replace r=matklad a=mikhail-m1 next steps: * ignore space and other minor difference * add support to ra_cli * call rust parser to check pattern * documentation original issue #2267 Co-authored-by: Mikhail Modin <[email protected]>
| * Init implementation of structural search replaceMikhail Modin2020-02-141-0/+5
| |
* | Add arguments to rustfmtIlya Titkov2020-02-171-2/+16
| |
* | vscode: added minimum bound for lruCapacity optionVeetaha2020-02-161-0/+2
| |
* | vscode: fix all integer -> number and add nullablitiy to maxInlayHintLengthVeetaha2020-02-161-5/+2
| |
* | vscode: update exclusiveMinimum validation according to JSONSchemaV4 specsVeetaha2020-02-161-1/+2
| |
* | vscode: add version and storage parameters to github binary sourceVeetaha2020-02-161-1/+1
| |
* | Merge #3131bors[bot]2020-02-141-0/+10
|\ \ | |/ |/| | | | | | | | | | | 3131: vscode: simplified config and to removed one source of truth of default values r=matklad a=Veetaha Though not intended initially, the implementation of config design is alike [dart's one](https://github.com/Dart-Code/Dart-Code/blob/master/src/extension/config.ts) as pointed by @matklad in PM. Co-authored-by: Veetaha <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 22:40:24 +0000