aboutsummaryrefslogtreecommitdiff
path: root/editors/code/package.json
Commit message (Collapse)AuthorAgeFilesLines
* Omit default parameter typesKirill Bulatov2019-12-191-0/+5
|
* 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
| |
* | added decorationsOmer Ben-Amram2019-12-141-1/+55
|/
* Code: enable prettier trailing commasLaurențiu Nicola2019-12-091-1/+2
|
* Add rollup sourcemap and fix launch.jsonEdwin Cheng2019-12-081-0/+1
|
* Code: bump depsLaurențiu Nicola2019-12-081-13/+13
|
* Code: check whether the LSP binary is in PATHLaurențiu Nicola2019-12-081-0/+1
|
* Use DocumentProvider instead of HoverEdwin Cheng2019-11-191-0/+5
|
* document feature flagsAleksey Kladov2019-10-251-5/+0
|
* Merge #1980bors[bot]2019-10-231-0/+5
|\ | | | | | | | | | | | | | | 1980: Shorten inline type hints r=matklad a=detrumi Implements #1946 Co-authored-by: Wilco Kusee <[email protected]>
| * Make inlay hint length configurableWilco Kusee2019-10-181-0/+5
| |
* | Adds config option for cargo-watch `--ignore` flagRoberto Vidal2019-10-171-0/+5
| |
* | Add rust-analyzer.showWorkspaceLoadedNotification to package.jsonLaurențiu Nicola2019-10-171-0/+5
| |
* | Merge #1984bors[bot]2019-10-101-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | 1984: Bump rollup and vsce r=matklad a=kjeremy I got sick of the vsce warning on install and noticed that rollup was also out of date. Co-authored-by: kjeremy <[email protected]>
| * | Bump rollup and vscekjeremy2019-10-101-2/+2
| |/
* / engine.vscode and @types/vscode should matchkjeremy2019-10-101-1/+1
|/
* add rollup bundler for vscode extensionJasperDeSutter2019-09-231-4/+8
|
* Update minimal required vscode version to 1.37Lucas Spits2019-09-101-1/+1
|
* add option to disable notifyAleksey Kladov2019-09-061-0/+5
|
* Switch to `@types/vscode` and `vscode-test`Bastian Köcher2019-08-261-4/+7
| | | | | | The old `vscode` package is outdated and it is recommened to switch to these two new packages. This also solves a problem of a missing `.d.ts` for `vscode` in Nixos.
* implement feature flagsAleksey Kladov2019-08-221-4/+4
|
* fix default for the exlude keyAleksey Kladov2019-08-211-1/+1
|
* allow to exclude certain files and directoriesAleksey Kladov2019-08-061-0/+5
|
* Merge #1614bors[bot]2019-07-291-1/+1
|\ | | | | | | | | | | | | | | 1614: show prettier diff on CI r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * show prettier diff on CIAleksey Kladov2019-07-291-1/+1
| |
* | :arrow_up: npmAleksey Kladov2019-07-291-6/+6
|/
* Show type decoratorsKirill Bulatov2019-07-251-0/+14
|
* try to show exact prettier problemAleksey Kladov2019-07-251-1/+1
|
* :arrow_up: npm depsAleksey Kladov2019-07-251-1/+1
|
* Remove obsolete keybindingAleksey Kladov2019-07-211-5/+0
|
* underline mutable bindingsAleksey Kladov2019-07-191-3/+3
|
* highlight mutable variables differentlyEkaterina Babshukova2019-07-181-0/+9
|
* Update vsce to latestkjeremy2019-07-031-1/+1
|
* Run VS Code tests on CIRyan Cumming2019-06-291-1/+1
| | | | | | | | | | | | | This is actually much faster than I expected; it takes about 13 seconds to download VS Code and run the unit tests. This means the VS Code tests are still significantly faster than the Rust ones. If this ends up being unreliable we can always remove it later or move it to a separate optional job. We also need to ignore the `.vscode-test` directory when running `prettier` or it will get upset about some temporary JSON files VS Code creates.
* Initial Visual Studio Code unit testsRyan Cumming2019-06-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As promised in #1439 this is an initial attempt at unit testing the VSCode extension. There are two separate parts to this: getting the test framework working and unit testing the code in #1439. The test framework nearly intact from the VSCode extension generator. The main thing missing was `test/index.ts` which acts as an entry point for Mocha. This was simply copied back in. I also needed to open the test VSCode instance inside a workspace as our file URI generation depends on a workspace being open. There are two ways to run the test framework: 1. Opening the extension's source in VSCode, pressing F5 and selecting the "Extensions Test" debug target. 2. Closing all copies of VSCode and running `npm test`. This is started from the command line but actually opens a temporary VSCode window to host the tests. This doesn't attempt to wire this up to CI. That requires running a headless X11 server which is a bit daunting. I'll assess the difficulty of that in a follow-up branch. This PR is at least helpful for local development without having to induce errors on a Rust project. For the actual tests this uses snapshots of `rustc` output from a real Rust project captured from the command line. Except for extracting the `message` object and reformatting they're copied verbatim into fixture JSON files. Only four different types of diagnostics are tested but they represent the main combinations of code actions and related information possible. They can be considered the happy path tests; as we encounter corner-cases we can introduce new tests fixtures.
* Fix code after "apply suggestions"Aleksei Sidorov2019-06-241-2/+2
|
* Apply suggestions from code reviewAleksey Sidorov2019-06-241-2/+2
| | | Co-Authored-By: Aleksey Kladov <[email protected]>
* Introduce cargo-watch.check-commandAleksei Sidorov2019-06-241-1/+6
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-26 19:43:08 +0000