Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Adds "restart server" command | Roberto Vidal | 2019-04-16 | 2 | -1/+20 | |
| | ||||||
* | Sends cwd info for runnables and code lenses | Roberto Vidal | 2019-04-14 | 1 | -1/+2 | |
| | ||||||
* | Adds support for multiple editor workspaces on initialization | Roberto Vidal | 2019-04-14 | 1 | -7/+0 | |
| | | | | This is a quick, partial fix for #1104 | |||||
* | Fix eslint errors | Emil Lauridsen | 2019-04-03 | 1 | -1/+1 | |
| | ||||||
* | Add extra double quotes only on Windows. | Emil Lauridsen | 2019-04-03 | 1 | -0/+4 | |
| | | | | | | As tested by @edwin0cheng, Windows requires the quotes removed in the previous commit. This commit re-adds the quotes gated by an if statement on the node environment, so that quotes are only added on Windows. | |||||
* | Fix VSCode cargo-watch functionality on Linux. | Emil Lauridsen | 2019-04-03 | 1 | -2/+1 | |
| | | | | | | | | | | | | | As of #1079 the VSCode cargo-watch functionality has been broken on Linux systems. The cause seems to be that linux takes the added quotes inside process arguments literally, so it attempts to make cargo-watch run the command `cargo "check --message-format json"` with the entire quoted part being treated as a single long subcommand, which cargo doesn't know how to handle. Removing the extra quotes solves the issue. | |||||
* | Add cargo-watch package animation and refactoring | Edwin Cheng | 2019-04-02 | 2 | -44/+78 | |
| | ||||||
* | Fix prettier error | Edwin Cheng | 2019-04-02 | 1 | -1/+1 | |
| | ||||||
* | Add terminate process implemntation note | Edwin Cheng | 2019-04-02 | 1 | -0/+7 | |
| | ||||||
* | Add Cargo.toml file check before cargo watch start | Edwin Cheng | 2019-04-02 | 1 | -0/+22 | |
| | ||||||
* | Add cargo-watch.check-arguments | Edwin Cheng | 2019-04-02 | 5 | -74/+137 | |
| | ||||||
* | Add config for cargo-watch trace | Edwin Cheng | 2019-04-02 | 4 | -15/+66 | |
| | ||||||
* | Add proper process teminate method | Edwin Cheng | 2019-04-02 | 6 | -10/+116 | |
| | ||||||
* | Fix prettier error | Edwin Cheng | 2019-04-02 | 4 | -22/+31 | |
| | ||||||
* | Fixed tslint error | Edwin Cheng | 2019-04-02 | 1 | -1/+1 | |
| | ||||||
* | Fix tslint error | Edwin Cheng | 2019-04-02 | 2 | -63/+65 | |
| | ||||||
* | Improve cargo-watch usage | Edwin Cheng | 2019-04-02 | 4 | -36/+177 | |
| | ||||||
* | Don't execute cargo watch when popup is dismissed | pcpthm | 2019-03-22 | 1 | -2/+2 | |
| | ||||||
* | Change enableCargoWatchOnStartup to have three states | Ville Penttinen | 2019-03-21 | 3 | -16/+31 | |
| | | | | | | | This fixes #1005. Defaults to `ask` which prompts users each time whether to start `cargo watch` or not. `enabled` always starts `cargo watch` and `disabled` does not. | |||||
* | Appease CI | Igor Matuszewski | 2019-03-18 | 1 | -9/+7 | |
| | ||||||
* | Guard auto cargo watch behind a config option | Igor Matuszewski | 2019-03-18 | 3 | -0/+17 | |
| | ||||||
* | Separate out the interactive cargo watch procedure | Igor Matuszewski | 2019-03-18 | 2 | -64/+70 | |
| | ||||||
* | Reformat using Prettier | Igor Matuszewski | 2019-03-18 | 2 | -17/+35 | |
| | ||||||
* | Remove unused imports | Igor Matuszewski | 2019-03-18 | 1 | -2/+1 | |
| | ||||||
* | Prefer installing `cargo-watch` via Task API | Igor Matuszewski | 2019-03-18 | 1 | -23/+14 | |
| | | | | This gives us much more fine-grained stdout buffering and ANSI terminal colors. | |||||
* | Respect the user-provided label when creating task | Igor Matuszewski | 2019-03-18 | 1 | -1/+1 | |
| | ||||||
* | Ask the user to install and start cargo watch | Igor Matuszewski | 2019-03-18 | 1 | -5/+61 | |
| | ||||||
* | Define a cargo watch task | Igor Matuszewski | 2019-03-18 | 1 | -1/+21 | |
| | ||||||
* | Remove redundant Runnable.range | Igor Matuszewski | 2019-03-18 | 1 | -1/+0 | |
| | ||||||
* | activate extension if Cargo.toml is present | Aleksey Kladov | 2019-03-13 | 1 | -1/+2 | |
| | ||||||
* | Applied code style of ``npm run fix`` | Lucas Spits | 2019-03-11 | 1 | -6/+4 | |
| | ||||||
* | Fix typescript linting errors | Lucas Spits | 2019-03-11 | 1 | -1/+1 | |
| | ||||||
* | Merge branch 'master' of https://github.com/LDSpits/rust-analyzer into ↵ | Lucas Spits | 2019-03-11 | 1 | -2/+2 | |
|\ | | | | | | | feature/workspace-directory | |||||
| * | prettier format | Bernardo | 2019-03-10 | 1 | -1/+1 | |
| | | ||||||
| * | simplify watch patterns | Bernardo | 2019-03-10 | 1 | -3/+3 | |
| | | ||||||
* | | Retrieve current directory from workspaces | Lucas Spits | 2019-03-11 | 1 | -2/+18 | |
|/ | ||||||
* | Add showWorkspaceLoadedNotification to vscode client | Ville Penttinen | 2019-03-06 | 3 | -1/+15 | |
| | | | | | | | | | This allows users to control whether or not they want to see the "workspace loaded" notification. This is done on the server side using InitializationOptions which are provided by the client. By default show_workspace_loaded is true, meaning the notification is sent. | |||||
* | Allow syntax tree to update when changing files | Ville Penttinen | 2019-03-03 | 2 | -17/+26 | |
| | | | | | | Previously when using the file based syntax tree, it would not update until a change had been made in the new file. Now we automatically update the syntax tree to match the current file. | |||||
* | Rename syntaxtree text provider to SyntaxTreeContentProvider | Ville Penttinen | 2019-03-03 | 3 | -13/+11 | |
| | ||||||
* | Add vscode support for range in SyntaxTreeParams | Ville Penttinen | 2019-03-03 | 3 | -11/+41 | |
| | | | | | | This enables the client to use a command to either show the live-updating version of the syntax tree for the current file. Or optionally when a selected range is provided, we then provide a snapshot of the syntax tree for the range. | |||||
* | Change default value of highlightingOn to false | Ville Penttinen | 2019-02-26 | 1 | -1/+1 | |
| | ||||||
* | Use named multiline Problem Matcher | kjeremy | 2019-02-18 | 1 | -29/+2 | |
| | | | | | Now that https://github.com/Microsoft/vscode/pull/65840 is in the latest release we can use the first commit from https://github.com/rust-analyzer/rust-analyzer/pull/408 | |||||
* | Specify vscode 1.31 | kjeremy | 2019-02-12 | 1 | -1/+1 | |
| | ||||||
* | Update dependencies | DJMcNab | 2019-02-10 | 2 | -8/+8 | |
| | ||||||
* | Fix trace and prettier | DJMcNab | 2019-02-10 | 1 | -2/+4 | |
| | ||||||
* | Add support for a seperate output channel for trace messages | DJMcNab | 2019-02-10 | 3 | -10/+13 | |
| | ||||||
* | Update npm packages | kjeremy | 2019-02-07 | 2 | -99/+65 | |
| | ||||||
* | Run prettier | Ville Penttinen | 2019-02-07 | 1 | -4/+11 | |
| | ||||||
* | Add new configuration "enableEnhancedTyping" to control registering of ↵ | Ville Penttinen | 2019-02-07 | 3 | -1/+33 | |
| | | | | | | | | | | | | | | | | | | "type" command This further fixes problems when having a VIM extension (at least vscodevim) enabled, by not calling `overrideCommand('type', commands.onEnter.handle)` when enableEnhancedTyping is set to `false`. The problem is dependent on the order in which extensions are activated, if rust-analyzer is activated before `vscodevim`, rust-analyzer will register the `type` command, and when `vscodevim` finally attempts to activate, it will fail to register the command. This causes `vscodevim` to stop working properly. This setting allows users to disable the registerCommand `type` in rust-analyzer, allowing `vscodevim` to work. The setting defaults to `true`. Currently changing the setting requires reloading of the window. | |||||
* | Implement lens for impls and support resolving lenses. | Jeremy Kolb | 2019-02-04 | 1 | -0/+12 | |
| |