Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
| * | | | | Fixed a typo | Omer Ben-Amram | 2019-12-16 | 1 | -1/+1 | |
| |/ / / | | | | | | | | | | | | | thanks @lnicola | |||||
* / / / | Default to client watching on VS Code | Aleksey Kladov | 2019-12-17 | 1 | -1/+1 | |
|/ / / | ||||||
* | | | Properly format json | Oliver Scherer | 2019-12-15 | 1 | -9/+11 | |
| | | | ||||||
* | | | Add a rudimentary json regex to get at information like `endLine` | Oliver Scherer | 2019-12-15 | 1 | -0/+20 | |
| | | | ||||||
* | | | Merge branch 'refs/heads/master' into feature/granular-scopes | Omer Ben-Amram | 2019-12-14 | 1 | -0/+15 | |
|\ \ \ | ||||||
| * | | | Enable `allFeatures` by default and fix lints | oxalica | 2019-12-13 | 1 | -1/+1 | |
| | | | | ||||||
| * | | | Support setting cargo features | oxalica | 2019-12-13 | 1 | -0/+15 | |
| | | | | ||||||
* | | | | removed `type.alias` | Omer Ben-Amram | 2019-12-14 | 1 | -0/+9 | |
| | | | | ||||||
* | | | | added decorations | Omer Ben-Amram | 2019-12-14 | 1 | -1/+55 | |
|/ / / | ||||||
* | | | Code: enable prettier trailing commas | Laurențiu Nicola | 2019-12-09 | 1 | -1/+2 | |
| | | | ||||||
* | | | Add rollup sourcemap and fix launch.json | Edwin Cheng | 2019-12-08 | 1 | -0/+1 | |
| | | | ||||||
* | | | Code: bump deps | Laurențiu Nicola | 2019-12-08 | 1 | -13/+13 | |
| | | | ||||||
* | | | Code: check whether the LSP binary is in PATH | Laurențiu Nicola | 2019-12-08 | 1 | -0/+1 | |
| |/ |/| | ||||||
* | | Use DocumentProvider instead of Hover | Edwin Cheng | 2019-11-19 | 1 | -0/+5 | |
|/ | ||||||
* | document feature flags | Aleksey Kladov | 2019-10-25 | 1 | -5/+0 | |
| | ||||||
* | Merge #1980 | bors[bot] | 2019-10-23 | 1 | -0/+5 | |
|\ | | | | | | | | | | | | | | | 1980: Shorten inline type hints r=matklad a=detrumi Implements #1946 Co-authored-by: Wilco Kusee <[email protected]> | |||||
| * | Make inlay hint length configurable | Wilco Kusee | 2019-10-18 | 1 | -0/+5 | |
| | | ||||||
* | | Adds config option for cargo-watch `--ignore` flag | Roberto Vidal | 2019-10-17 | 1 | -0/+5 | |
| | | ||||||
* | | Add rust-analyzer.showWorkspaceLoadedNotification to package.json | Laurențiu Nicola | 2019-10-17 | 1 | -0/+5 | |
| | | ||||||
* | | Merge #1984 | bors[bot] | 2019-10-10 | 1 | -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 vsce | kjeremy | 2019-10-10 | 1 | -2/+2 | |
| |/ | ||||||
* / | engine.vscode and @types/vscode should match | kjeremy | 2019-10-10 | 1 | -1/+1 | |
|/ | ||||||
* | add rollup bundler for vscode extension | JasperDeSutter | 2019-09-23 | 1 | -4/+8 | |
| | ||||||
* | Update minimal required vscode version to 1.37 | Lucas Spits | 2019-09-10 | 1 | -1/+1 | |
| | ||||||
* | add option to disable notify | Aleksey Kladov | 2019-09-06 | 1 | -0/+5 | |
| | ||||||
* | Switch to `@types/vscode` and `vscode-test` | Bastian Köcher | 2019-08-26 | 1 | -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 flags | Aleksey Kladov | 2019-08-22 | 1 | -4/+4 | |
| | ||||||
* | fix default for the exlude key | Aleksey Kladov | 2019-08-21 | 1 | -1/+1 | |
| | ||||||
* | allow to exclude certain files and directories | Aleksey Kladov | 2019-08-06 | 1 | -0/+5 | |
| | ||||||
* | Merge #1614 | bors[bot] | 2019-07-29 | 1 | -1/+1 | |
|\ | | | | | | | | | | | | | | | 1614: show prettier diff on CI r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]> | |||||
| * | show prettier diff on CI | Aleksey Kladov | 2019-07-29 | 1 | -1/+1 | |
| | | ||||||
* | | :arrow_up: npm | Aleksey Kladov | 2019-07-29 | 1 | -6/+6 | |
|/ | ||||||
* | Show type decorators | Kirill Bulatov | 2019-07-25 | 1 | -0/+14 | |
| | ||||||
* | try to show exact prettier problem | Aleksey Kladov | 2019-07-25 | 1 | -1/+1 | |
| | ||||||
* | :arrow_up: npm deps | Aleksey Kladov | 2019-07-25 | 1 | -1/+1 | |
| | ||||||
* | Remove obsolete keybinding | Aleksey Kladov | 2019-07-21 | 1 | -5/+0 | |
| | ||||||
* | underline mutable bindings | Aleksey Kladov | 2019-07-19 | 1 | -3/+3 | |
| | ||||||
* | highlight mutable variables differently | Ekaterina Babshukova | 2019-07-18 | 1 | -0/+9 | |
| | ||||||
* | Update vsce to latest | kjeremy | 2019-07-03 | 1 | -1/+1 | |
| | ||||||
* | Run VS Code tests on CI | Ryan Cumming | 2019-06-29 | 1 | -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 tests | Ryan Cumming | 2019-06-26 | 1 | -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 Sidorov | 2019-06-24 | 1 | -2/+2 | |
| | ||||||
* | Apply suggestions from code review | Aleksey Sidorov | 2019-06-24 | 1 | -2/+2 | |
| | | | Co-Authored-By: Aleksey Kladov <[email protected]> | |||||
* | Introduce cargo-watch.check-command | Aleksei Sidorov | 2019-06-24 | 1 | -1/+6 | |
| | ||||||
* | make LRU cache configurable | Aleksey Kladov | 2019-06-12 | 1 | -0/+5 | |
| | ||||||
* | Make rainbows optional | Pascal Hertleif | 2019-05-27 | 1 | -0/+5 | |
| | ||||||
* | Semantic highlighting spike | Pascal Hertleif | 2019-05-27 | 1 | -0/+2 | |
| | | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request? | |||||
* | Improve highlighting of name refs | Laurențiu Nicola | 2019-05-23 | 1 | -1/+46 | |
| | ||||||
* | Address feedback | Laurențiu Nicola | 2019-05-21 | 1 | -28/+19 | |
| | ||||||
* | Use ThemeColor and add support for light themes | Laurențiu Nicola | 2019-05-21 | 1 | -0/+119 | |
| |