aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
...
* 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]>
| * vscode: moved tslib to runtime dependencies and added \"importHelpers\": trueVeetaha2020-02-011-2/+2
| |
* | fix repo link in package.jsonVeetaha2020-02-021-1/+2
|/
* :arrow_up: nodeAleksey Kladov2020-01-281-6/+6
|
* vscode-languageclient 6.1.0kjeremy2020-01-271-1/+1
| | | | Adds support for proposed semantic highlighting extension
* vscode-languageclient 6.0.1Jeremy Kolb2020-01-211-1/+1
|
* Merge #2843bors[bot]2020-01-151-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | 2843: Add inlay parameter name hints for call expr r=matklad a=imtsuki This patch adds Intellij-like parameter name hints for literal values in function calls. <img width="624" alt="Screenshot" src="https://user-images.githubusercontent.com/8423594/72366533-68d7f800-3735-11ea-9279-cf193ca8ca2f.png"> Signed-off-by: imtsuki <[email protected]> Co-authored-by: imtsuki <[email protected]>
| * Add inlay parameter name hints for function callsimtsuki2020-01-141-1/+1
| | | | | | | | Signed-off-by: imtsuki <[email protected]>
* | Language Server Protocol 3.15 is now stablekjeremy2020-01-141-1/+1
| | | | | | | | Update the client
* | vscode-languageclient 6.0.0-next.10kjeremy2020-01-131-1/+1
|/
* Rename VS Code extension to rust-analyzerAleksey Kladov2020-01-131-3/+4
|
* Fix lruCapacity config setting typeMarco Groppo2020-01-111-1/+4
|
* Add semicolonsAleksey Kladov2019-12-311-1/+2
|
* Fix color nameAleksey Kladov2019-12-311-1/+1
|
* Drop obsolete color configurationsAleksey Kladov2019-12-311-288/+1
|
* Add tsfmtAleksey Kladov2019-12-301-1/+3
|
* Remove prettierAleksey Kladov2019-12-301-8/+1
|
* Run prettier on all filesAleksey Kladov2019-12-301-1/+1
|
* Add prettierAleksey Kladov2019-12-301-6/+13
|
* Rename extension.ts -> main.tsAleksey Kladov2019-12-301-1/+1
|
* Add rollupAleksey Kladov2019-12-301-7/+12
|
* Minimize TypeScript buildAleksey Kladov2019-12-301-35/+8
|
* Merge #2061bors[bot]2019-12-291-1/+64
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2061: Theme loading and "editor.tokenColorCustomizations" support. r=matklad a=seivan Fixes: [Issue#1294](https://github.com/rust-analyzer/rust-analyzer/issues/1294#issuecomment-497450325) TODO: - [x] Load themes - [x] Load existing `ralsp`-prefixed overrides from `"workbench.colorCustomizations"`. - [x] Load overrides from `"editor.tokenColorCustomizations.textMateRules"`. - [x] Use RA tags to load `vscode.DecorationRenderOptions` (colors) from theme & overrides. - [x] Map RA tags to common TextMate scopes before loading colors. - [x] Add default scope mappings in extension. - [x] Cache mappings between settings updates. - [x] Add scope mapping configuration manifest in `package.json` - [x] Load configurable scope mappings from settings. - [x] Load JSON Scheme for text mate scope rules in settings. - [x] Update [Readme](https://github.com/seivan/rust-analyzer/blob/feature/themes/docs/user/README.md#settings). Borrowed the theme loading (`scopes.ts`) from `Tree Sitter` with some modifications to reading `"editor.tokenColorCustomizations"` for merging with loaded themes and had to remove the async portions to be able to load it from settings updates. ~Just a PoC and an idea I toyed around with a lot of room for improvement.~ For starters, certain keywords aren't part of the standard TextMate grammar, so it still reads colors from the `ralsp` prefixed values in `"workbench.colorCustomizations"`. But I think there's more value making the extension work with existing themes by maping some of the decoration tags to existing key or keys. <img width="453" alt="Screenshot 2019-11-09 at 17 43 18" src="https://user-images.githubusercontent.com/55424/68531968-71b4e380-0318-11ea-924e-cdbb8d5eae06.png"> <img width="780" alt="Screenshot 2019-11-09 at 17 41 45" src="https://user-images.githubusercontent.com/55424/68531950-4b8f4380-0318-11ea-8f85-24a84efaf23b.png"> <img width="468" alt="Screenshot 2019-11-09 at 17 40 29" src="https://user-images.githubusercontent.com/55424/68531952-51852480-0318-11ea-800a-6ae9215f5368.png"> These will merge with the default ones coming with the extension, so you don't have to implement all of them and works well with overrides defined in settings. ```jsonc "editor.tokenColorCustomizations": { "textMateRules": [ { "scope": "keyword", "settings": { "fontStyle": "bold", } }, ] }, ``` Edit: The idea is to work with 90% of the themes out there by working within existing scopes available that are generally styled. It's not to say I want to erase the custom Rust scopes - those should still remain and eventually worked into a custom grammar bundle for Rust specific themes that target those, I just want to make it work with generic themes offered on the market place for now. A custom grammar bundle and themes for Rust specific scopes is out of... scope for this PR. We'll make another round to tackle those issues. Current fallbacks implemented ```typescript [ 'comment', [ 'comment', 'comment.block', 'comment.line', 'comment.block.documentation' ] ], ['string', ['string']], ['keyword', ['keyword']], ['keyword.control', ['keyword.control', 'keyword', 'keyword.other']], [ 'keyword.unsafe', ['storage.modifier', 'keyword.other', 'keyword.control', 'keyword'] ], ['function', ['entity.name.function']], ['parameter', ['variable.parameter']], ['constant', ['constant', 'variable']], ['type', ['entity.name.type']], ['builtin', ['variable.language', 'support.type', 'support.type']], ['text', ['string', 'string.quoted', 'string.regexp']], ['attribute', ['keyword']], ['literal', ['string', 'string.quoted', 'string.regexp']], ['macro', ['support.other']], ['variable', ['variable']], ['variable.mut', ['variable', 'storage.modifier']], [ 'field', [ 'variable.object.property', 'meta.field.declaration', 'meta.definition.property', 'variable.other' ] ], ['module', ['entity.name.section', 'entity.other']] ``` Co-authored-by: Seivan Heidari <[email protected]>
| * Merge branch 'master' into feature/themesSeivan Heidari2019-12-231-16/+125
| |\
| * \ Merge branch 'master' of https://github.com/rust-analyzer/rust-analyzer into ↵Seivan Heidari2019-11-201-0/+5
| |\ \ | | | | | | | | | | | | feature/themes
| * | | Readding jsonc parser because of ↵Seivan Heidari2019-11-181-1/+2
| | | | | | | | | | | | | | | | https://github.com/rust-analyzer/rust-analyzer/pull/2061\#discussion_r344783715
| * | | Vscode wasn't running the linter automatically so ran `npm run fix` - wonder ↵Seivan Heidari2019-11-091-1/+1
| | | | | | | | | | | | | | | | if it's related to `tslint` being deprecated.
| * | | * Adding scope mapping configuration manifest in `package.json`Seivan Heidari2019-11-041-1/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Loading configurable scope mappings from settings. * Updating Readme with `rust-analyzer.scopeMappings`. `rust-analyzer.scopeMappings` -- a scheme backed JSON object to tweak Rust Analyzer scopes to TextMate scopes. ```jsonc { //Will autocomplete keys to available RA scopes. "keyword.unsafe": ["keyword", "keyword.control"], //Values are string | TextMateScope | [string | TextMateScope] "comments": "comment.block" } ```
* | | | Keep VSCode config mostly backwards compatibleEmil Lauridsen2019-12-251-20/+14
| | | |
* | | | Configuration plumbing for cargo watcherEmil Lauridsen2019-12-251-30/+10
| | | |
* | | | Remove cargo-watch from vscode extension.Emil Lauridsen2019-12-251-11/+1
| |_|/ |/| | | | | | | | Still keeps tests around for reference when porting them to rust
* | | Update to latest packageskjeremy2019-12-201-8/+8
| | |
* | | Merge #2583bors[bot]2019-12-171-1/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2583: Use prettier settings in ts-lint r=matklad a=edwin0cheng This PR add `tslint-plugin-prettier` extension in ts-lint, which "runs prettier rules as tslint rules." and remove `quotemark` from ts-lint and let prettier to handle it. And also fix #2515 Co-authored-by: Edwin Cheng <[email protected]>
| * | | use pretter settings in ts-lintEdwin Cheng2019-12-171-1/+2
| | | |
* | | | Merge #2568bors[bot]2019-12-171-0/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2568: Add option to disable all-targets. r=matklad a=pftbest Can be useful in embedded. Co-authored-by: Vadzim Dambrouski <[email protected]>
| * | | | Add option to disable all-targets.Vadzim Dambrouski2019-12-151-0/+5
| |/ / / | | | | | | | | | | | | Can be useful in embedded.
* | | | Merge #2571bors[bot]2019-12-171-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2571: Fixed a typo in settings r=matklad a=omerbenamram @lnicola found a typo in the description for one of the settings introduced in #2559. Co-authored-by: Omer Ben-Amram <[email protected]>
| * | | | Fixed a typoOmer Ben-Amram2019-12-161-1/+1
| |/ / / | | | | | | | | | | | | thanks @lnicola
* / / / Default to client watching on VS CodeAleksey Kladov2019-12-171-1/+1
|/ / /
* | | Properly format jsonOliver Scherer2019-12-151-9/+11
| | |
* | | Add a rudimentary json regex to get at information like `endLine`Oliver Scherer2019-12-151-0/+20
| | |
* | | Merge branch 'refs/heads/master' into feature/granular-scopesOmer Ben-Amram2019-12-141-0/+15
|\ \ \
| * | | Enable `allFeatures` by default and fix lintsoxalica2019-12-131-1/+1
| | | |
| * | | Support setting cargo featuresoxalica2019-12-131-0/+15
| | | |
* | | | removed `type.alias`Omer Ben-Amram2019-12-141-0/+9
| | | |