Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | vscode-postrefactor: enforcing more reentrancy | Veetaha | 2020-03-14 | 2 | -4/+7 |
| | |||||
* | vscode-postrefactor: minor config refactorings | Veetaha | 2020-03-14 | 2 | -4/+5 |
| | |||||
* | vscode-postrefactor: unhandled promise rejections shall not pass 2 | Veetaha | 2020-03-14 | 1 | -1/+1 |
| | |||||
* | vscode-postrefactor: add achtung comment | Veetaha | 2020-03-14 | 1 | -0/+4 |
| | |||||
* | vscode-postrefactor: remove remainders of debug logging | Veetaha | 2020-03-14 | 1 | -1/+0 |
| | |||||
* | vscode-postrefactor: unhandled promise rejections shall not pass | Veetaha | 2020-03-14 | 1 | -1/+1 |
| | |||||
* | vscode-postrefactor: compare dates by value, not by reference | Veetaha | 2020-03-14 | 1 | -2/+2 |
| | |||||
* | vscode-postrefactor: eliminate my-mistake floating promise @matklad | Veetaha | 2020-03-14 | 1 | -1/+1 |
| | |||||
* | vscode-postrefactor: global storages | Veetaha | 2020-03-14 | 1 | -20/+19 |
| | |||||
* | vscode: put comma back | Veetaha | 2020-03-14 | 1 | -1/+1 |
| | |||||
* | vscode: make bailing out on custom serverPath more evident | Veetaha | 2020-03-14 | 2 | -10/+8 |
| | |||||
* | vscode: npm run fix | Veetaha | 2020-03-14 | 2 | -4/+4 |
| | |||||
* | vscode: amend server installation logic to account for nightlies | Veetaha | 2020-03-14 | 3 | -52/+57 |
| | |||||
* | vscode: add nightly extension installation logic | Veetaha | 2020-03-14 | 1 | -0/+131 |
| | |||||
* | vscode: prepare config for nightlies | Veetaha | 2020-03-14 | 1 | -15/+96 |
| | |||||
* | vscode: get release date from release info | Veetaha | 2020-03-14 | 2 | -14/+7 |
| | |||||
* | vscode-prerefactor: add some utility functions | Veetaha | 2020-03-14 | 1 | -6/+63 |
| | |||||
* | vscode-prerefactor: merge two files into downloads.ts | Veetaha | 2020-03-14 | 2 | -50/+46 |
| | |||||
* | Simpler deserialization | Aleksey Kladov | 2020-03-12 | 1 | -1/+6 |
| | |||||
* | Merge #3543 | bors[bot] | 2020-03-12 | 3 | -5/+17 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | 3543: Parameter inlay hint separate from variable type inlay? #2876 r=matklad a=slyngbaek Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side Co-authored-by: Steffen Lyngbaek <[email protected]> | ||||
| * | Make maxLength nullable again | Steffen Lyngbaek | 2020-03-12 | 1 | -2/+2 |
| | | |||||
| * | Switch from Vec<InlayKind> to object with props | Steffen Lyngbaek | 2020-03-12 | 3 | -8/+9 |
| | | | | | | | | | | | | | | - Instead of a single object type, use several individual nested types to allow toggling from the settings GUI - Remove unused struct definitions - Install and test that the toggles work | ||||
| * | Address Issues from Github | Steffen Lyngbaek | 2020-03-10 | 1 | -1/+3 |
| | | | | | | | | | | | | | | - Updated naming of config - Define struct in ra_ide and use remote derive in rust-analyzer/config - Make inlayConfig type more flexible to support more future types - Remove constructor only used in tests | ||||
| * | Parameter inlay hint separate from variable type inlay? #2876 | Steffen Lyngbaek | 2020-03-10 | 3 | -4/+13 |
| | | | | | | | | | | | | | | | | | | Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side | ||||
* | | Add additional_outdirs in config | Edwin Cheng | 2020-03-10 | 2 | -0/+2 |
|/ | |||||
* | vscode: groupd updates-related config under `updates` section as per @matklad | Veetaha | 2020-03-09 | 1 | -1/+1 |
| | |||||
* | vscode: fix inversion of askBeforeDownload | Veetaha | 2020-03-08 | 1 | -1/+1 |
| | |||||
* | vscode: rename alwaysDownloadServer -> askBeforeDownload | Veetaha | 2020-03-08 | 1 | -1/+1 |
| | | | | | | | | | | | The new name seems much simpler and it doesn't limit this config value only to downloading the server binary. Thus we wouldn't need to create another config properties to handle other downloads whatsoever. Anyway, I believe (heuristically) that most of the users would want to set "askBeforeDownload": false once and never bother clicking on the notification again (because otherwise there is no big point in installing rust-analyzer if it cannot install the server) | ||||
* | vscode: care about alwaysDownloadServer option before asking | Veetaha | 2020-03-07 | 3 | -23/+31 |
| | | | | | | | Also renamed BinarySource to ArtifactSource in anticipation of nightlies installation that requires downloading not a binary itself but .vsix package, thus generalized to `artifact` term | ||||
* | vscode: post refactor HintsUpdater (simplify create() -> constructor call) | Veetaha | 2020-03-07 | 1 | -16/+10 |
| | |||||
* | vscode: more privacy for HintsUpdater | Veetaha | 2020-03-07 | 1 | -1/+1 |
| | |||||
* | vscode: remove logging from inlays, run fix lint issues | Veetaha | 2020-03-07 | 1 | -18/+7 |
| | |||||
* | vscode: remove logic for caching editors as per @matklad | Veetaha | 2020-03-07 | 1 | -222/+136 |
| | |||||
* | vscode: prerefactor util.ts and ctx.ts | Veetaha | 2020-03-07 | 2 | -10/+14 |
| | |||||
* | vscode: refresh all editors on text changes, simplify inlays api | Veetaha | 2020-03-07 | 1 | -13/+11 |
| | |||||
* | vscode: add dat semicolon | Veetaha | 2020-03-07 | 1 | -1/+1 |
| | |||||
* | vscode: simpify | Veetaha | 2020-03-07 | 1 | -5/+1 |
| | |||||
* | vscode: redesign inlay hints to be capable of handling multiple editors | Veetaha | 2020-03-07 | 2 | -106/+273 |
| | |||||
* | vscode: extract Type and Param hint cases of InlayHint at type level (needed ↵ | Veetaha | 2020-03-07 | 1 | -8/+14 |
| | | | | further) | ||||
* | Merge #3388 | bors[bot] | 2020-03-03 | 5 | -15/+25 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3388: Remove inlay hint in diff views r=matklad a=vbfox If the left side of a diff view that contain the old version of the file apply inlays they are misplaced and produce a weird display: ![image](https://user-images.githubusercontent.com/131878/75628802-b1ac1900-5bdc-11ea-8c26-6722d8e38371.png) After the change: ![image](https://user-images.githubusercontent.com/131878/75628831-e91ac580-5bdc-11ea-9039-c6b4ffbdb2be.png) The detection is done by blacklisting the url schemes used by git and subversion scm extensions, whitelisting `file` is also possible but neither is perfect as VSCode now support both pluggable scm extensions and pluggable remote filesystems. But I suspect that the list of scm extensions is more easily manageable. **Note**: I can rebase on #3378 if needed as it touches the same lines of code Co-authored-by: Julien Roncaglia <[email protected]> | ||||
| * | Centralize the check for languageId on document | Julien Roncaglia | 2020-03-02 | 5 | -24/+25 |
| | | | | | | | | Also move visibleRustEditors to Ctx | ||||
| * | Remove inlay in diff views | Julien Roncaglia | 2020-03-01 | 1 | -1/+10 |
| | | | | | | | | | | | | | | | | If the left side of a diff view that contain the old version of the file apply inlays they are misplaced. The detection is done by blacklisting the url schemes used by git and subversion scm extensions. | ||||
* | | Don't fail loudly if the old highlighting breaks | Aleksey Kladov | 2020-03-02 | 1 | -4/+6 |
|/ | |||||
* | vscode: simplify assert.eq() to assert() as per matklad | Veetaha | 2020-02-28 | 2 | -15/+4 |
| | |||||
* | vscode: add dat semicolon | Veetaha | 2020-02-28 | 1 | -1/+1 |
| | |||||
* | vscode: add equality assertion | Veetaha | 2020-02-28 | 2 | -2/+12 |
| | |||||
* | vscode: rename nodeAssert -> nativeAssert | Veetaha | 2020-02-28 | 1 | -2/+2 |
| | |||||
* | vscode: add error loging on failed assertion | Veetaha | 2020-02-28 | 1 | -1/+6 |
| | |||||
* | vscode: migrate to more type-safe assert impl | Veetaha | 2020-02-28 | 3 | -8/+10 |
| | |||||
* | Reset fontStyle for inlay hints | Aleksey Kladov | 2020-02-28 | 1 | -0/+2 |
| | | | | Otherwise, we get bold hints on `true` and `false` |