Lukas Wirth
073a63b93e
feat: Allow viewing the full compiler diagnostic in a readonly textview
2022-11-18 19:56:08 +01:00
Lukas Wirth
fccf8eb1fd
Properly handle vscode workspace changes
2022-10-29 01:41:02 +02:00
Lukas Wirth
2071d00fd2
Always set up VSCode commands
2022-10-29 00:44:37 +02:00
Lukas Wirth
274df54885
feat: Clicking the status bar item stops and starts the server
2022-10-28 23:10:10 +02:00
Lukas Wirth
1cb46079e4
internal: Properly handle commands in the VSCode client when the server is stopped
2022-10-21 16:00:43 +02:00
Lukas Wirth
a8e0a20ce4
internal: Properly handle language configuration config changes
2022-10-20 21:14:36 +02:00
Lukas Wirth
d63c44e650
Cleanup output channels
2022-10-17 16:01:39 +02:00
Lukas Wirth
0421756b42
Implement stop and start server commands
2022-10-17 15:45:57 +02:00
Lukas Wirth
d68616a140
Make more things private
2022-10-17 15:05:20 +02:00
Lukas Wirth
8aaafddee8
Properly reload changed configs for server start
2022-10-17 14:53:46 +02:00
Lukas Wirth
6f435977df
Refactor language client handling
2022-10-17 14:21:12 +02:00
Jonas Schievink
55fdcbe339
Revert "fix: in VSCode, correctly resolve relative paths to errors"
2022-10-14 09:28:44 +02:00
Aleksey Kladov
5bbfea03cc
fix: in VSCode, correctly resolve relative paths to errors
...
VS Code problem matcher are restricted to be static "regexes". You can't
create a problem matcher dynamically, and you can't use custom code in
lieu of problem matcher.
This creates a problem for rust/cargo compiler errors. They use paths
relative to the root of the Cargo workspace, but VS Code doesn't
necessary know where that root is.
Luckily, there's a way out: our current problem matcher is defined like
this:
"fileLocation": [ "autoDetect", "${workspaceRoot}" ],
That means that relative pahts would be resoleved relative to workspace
root. VS Code allows to specify a command inside `${}`. So we can plug
custom logic there to fetch Cargo's workspace root!
And that's exactly what this PR is doing!
2022-10-08 23:25:13 +01:00
bors
fbb1337eb3
Auto merge of #12850 - Veykril:display-fix, r=Veykril
...
fix: Fix error tooltip message for VSCode status bar item
2022-07-22 22:52:53 +00:00
Lukas Wirth
e223d20d97
fix: Fix error tooltip message for VSCode status bar item
2022-07-23 00:52:12 +02:00
Lukas Wirth
f1b5e38563
Revert 03a62c180e
2022-07-23 00:14:34 +02:00
Lukas Wirth
def89af1ef
fix: Fix VSCode status bar tooltip not showing the error messages
2022-07-13 13:26:23 +02:00
Laurențiu Nicola
03a62c180e
Bump vscode-languageclient
2022-07-09 23:04:14 +03:00
Lukas Wirth
664a751f2b
fix: Clear proc-macro changed flag when reloading workspace
2022-06-15 14:29:13 +02:00
Lukas Wirth
1127d2508f
internal: Keep output channels across restarts
2022-06-05 14:20:06 +02:00
Lukas Wirth
fd298b3994
fix: Cleanup output channels when restarting server
2022-06-05 13:24:39 +02:00
Jake Heinz
a965161dce
[editors/vscode] cleaer status bar bg color / command when server status returns to OK
2022-06-01 06:58:16 +00:00
Lukas Wirth
02c2377229
internal: Use statusBarItem colors for status item in VSCode
2022-05-26 12:31:07 +02:00
Andrei Listochkin
f247090558
prettier run
2022-05-17 18:15:06 +01:00
Lukas Wirth
d6dba1c97c
auto update old configurations to newer ones
2022-05-01 19:57:09 +02:00
André Oliveira
8a563e4a46
Use local node_modules to allow the graph to load offline
...
- Fix some warnings
2021-08-10 13:43:08 +00:00
Milo
b8eeef4dfa
fix
2021-06-07 17:56:40 +01:00
Milo
42e5e5b458
fix
2021-06-06 00:21:50 +01:00
Milo
ab57c25d1e
when you click status bar icon it now restarts server
2021-06-06 00:17:16 +01:00
Kirill Bulatov
a05163db14
Create tasks for all workspaces
2021-05-26 01:11:52 +03:00
Kirill Bulatov
c1f6a5a0b0
Fix ts lint errors
2021-05-23 23:47:58 +03:00
Kirill Bulatov
b3383b0661
Send detached files info to server via init params
2021-05-23 22:46:20 +03:00
Kirill Bulatov
d9a5490646
Start rust-analyzer server for arbitrary rust files
2021-05-23 22:46:20 +03:00
Aleksey Kladov
ad02bfe58f
Sacrifice for the semicolon god
2021-04-06 15:50:02 +03:00
Aleksey Kladov
8fe20b19d4
More robust status notifications
2021-04-06 15:45:31 +03:00
Edwin Cheng
35310f1032
Update vscode for new status
2021-01-29 01:04:14 +08:00
lf-
f7f6ac3554
Add an option for extra env vars in the Code extension
2020-12-30 04:51:07 -08:00
kjeremy
b527257330
Move to vscode-languageclient 7.0.0-next.9
...
Stabilizes call hierarchy and semantic tokens features.
2020-09-02 09:40:59 -04:00
vsrs
1eed036a6e
Fix StatusNotification
2020-08-17 14:56:27 +03:00
Aleksey Kladov
3ef7676076
Implement StatusBar
2020-07-02 15:32:14 +02:00
veetaha
5f88df82a6
Remove unnecessary async from vscode language client creation
2020-04-25 20:52:50 +03:00
kjeremy
6f0f86d2c5
Enable the SemanticTokensFeature by default
...
This is covered under vscode's "editor.semanticHighlighting.enabled"
setting plus the user has to have a theme that has opted into highlighting.
Bumps required vscode stable to 1.44
2020-04-08 15:45:39 -04:00
Aleksey Kladov
48c58309cc
Lean onto default implementation of configs
2020-04-02 12:47:58 +02:00
Tim
3eb45b9922
Pass string instread of WorkspaceFolder
2020-03-31 10:24:01 +01:00
Tim
a781a58fe2
Throw error if no folder is opened
2020-03-31 09:06:52 +01:00
Tim
768aa4259f
Add basic task support
...
This adds basic support for running `cargo build`, `cargo run`, etc.
2020-03-30 21:23:21 +01:00
Kirill Bulatov
8a23bec2cd
Style fixes
2020-03-30 13:39:14 +03:00
Kirill Bulatov
a9dd442733
Send the config from the client
2020-03-30 13:39:14 +03:00
Aleksey Kladov
fb6e655de8
Rewrite auto-update
...
Everything now happens in main.ts, in the bootstrap family of
functions. The current flow is:
* check everything only on extension installation.
* if the user is on nightly channel, try to download the nightly
extension and reload.
* when we install nightly extension, we persist its release id, so
that we can check if the current release is different.
* if server binary was not downloaded by the current version of the
extension, redownload it (we persist the version of ext that
downloaded the server).
2020-03-19 09:04:59 +01:00
Aleksey Kladov
ae662617a2
Separate persistent mutable state from config
...
That way, we clearly see which things are not change, and we also
clearly see which things are persistent.
2020-03-16 22:02:11 +01:00
