aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
...
* 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]>
| * vscode: added more type safety to package.json configVeetaha2020-02-131-0/+10
| |
* | Expect vscode 1.42kjeremy2020-02-141-3/+3
| |
* | Prevent auto-update of dev extensionAleksey Kladov2020-02-141-1/+2
|/
* vscode: replaced unwrapNotNil() with ! as per @matkladVeetaha2020-02-091-1/+0
|
* vscode: amended config to use binary from globalStoragePath, added ui for ↵Veetaha2020-02-081-2/+4
| | | | downloading
* added fetchLatestArtifactMetadata() and downloadFile() functionsVeetaha2020-02-081-1/+5
|
* vscode: eliminate floating promises and insane amount of resource handle leaksVeetaha2020-02-051-1/+1
|
* vscode: Only handle enter if the suggest widget is hidden.Gregoire Geis2020-02-031-1/+1
|
* Remove enableEnhancedTyping and type overriding infrastructure.Gregoire Geis2020-02-031-5/+0
|
* Change default enhanced typing behavior from using type to using keybindings.Gregoire Geis2020-02-031-1/+6
|
* Add regular onEnter command, allowing onEnter to be called without ↵Gregoire Geis2020-02-031-0/+5
| | | | overriding the type command.
* Remove unnecessary flagsAleksey Kladov2020-02-031-2/+2
|
* Remove rollup-typescriptAleksey Kladov2020-02-031-2/+1
| | | | It seems like just calling typescript directly is simpler and more reliable?
* Update some rollup packagesAleksey Kladov2020-02-031-3/+3
|
* Use simple prng instead of a dependencyAleksey Kladov2020-02-031-2/+0
| | | | closes #2999
* Remove recent improvements to the build scriptAleksey Kladov2020-02-031-4/+4
| | | | | | | | tslib as a dev dependency and commonjs modules are definitely *wrong* in the ideal world, **but** in the real world that's the only combination that works. See https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Problems.20with.20TypeScript.20build
* vscode: dropped npm-check-updates scriptVeetaha2020-02-021-4/+1
|
* vscode: updated rollup typescript so it typechecks the bundleVeetaha2020-02-021-2/+5
|
* Merge #2979bors[bot]2020-02-021-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2979: vscode: now we are actually using tslib r=matklad a=Veetaha We had an incorrect setup where `tslib` was in `devDependencies`. FYI: tslib is a runtime dependency, it contains functions that are used by transpiled JavaScript in order not to inline them in each file. For example: ```ts // foo.ts (source code) import * as foo from "foo"; // --------------------------- // foo.js (compiled output) "use strict"; var __importStar = (this && this.__importStar) || function (mod) { if (mod && mod.__esModule) return mod; var result = {}; if (mod != null) for (var k in mod) if (Object.hasOwnProperty.call(mod, k)) result[k] = mod[k]; result["default"] = mod; return result; }; Object.defineProperty(exports, "__esModule", { value: true }); const foo = __importStar(require("foo")); ``` As you see, `tsc` generated that `__importStar` helper function in compiled output. And it generates it per each file if you don't enable `"importHelpers": true`. Now with `importHelpers` enabled we get the following picture: ```ts // foo.ts (source code) import * as foo from "foo"; // --------------------------- // foo.js (compiled output) "use strict"; Object.defineProperty(exports, "__esModule", { value: true }); const tslib_1 = require("tslib"); const foo = tslib_1.__importStar(require("foo")); ``` It saves some bundle size, but I am not entirely sure wheter we want that. Discussions are welcome! Co-authored-by: Veetaha <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 10:29:03 +0000