While working on #8641, I found a lot of places where we unnecessarily use `ref` / `ref mut` in match arms. In many cases, we're creating double-references (turning a `&T` into a `&&T`). The compiler should be smart enough to remove them for us, but there doesn't seem much point in explicitly creating double-references when we don't actually want them, and relying on compiler to optimize them out again. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
oxc_language_server
This crate provides an LSP Server which is used inside an editor or IDE.
Server Capabilities
- Text Document Synchronization:
FULL, - Workspace
- Workspace Folders:
true - File Operations:
false
- Workspace Folders:
- Code Actions Provider:
quickfixsource.fixAll.oxc, behaves the same asquickfixonly used when theCodeActionContext#onlycontainssource.fixAll.oxc.
Supported LSP Specifications from Server
- initialize
- Returns the Server Capabilities
- initialized
- shutdown
Workspace
workspace/didChangeConfiguration
The server expects this request when settings like run, enable or configPath are changed.
The server will revalidate or reset the diagnostics for all open files and send one or more textDocument/publishDiagnostics requests to the client.
workspace/didChangeWatchedFiles
The server expects this request when the oxlint configuration is changed. The server will revalidate the diagnostics for all open files and send one or more textDocument/publishDiagnostics requests to the client.
TextDocument
textDocument/didOpen
The server will validate the file content and send a textDocument/publishDiagnostics request to the client.
textDocument/didSave
When the configuration run is set to onSave, the server will validate the file content and send a textDocument/publishDiagnostics request to the client.
textDocument/didChange
When the configuration run is set to onType, the server will validate the file content and send a textDocument/publishDiagnostics request to the client.
textDocument/didClose
It will remove the reference internal.
textDocument/codeAction
Returns a list of CodeAction
Expected LSP Specification from Client
TextDocument
textDocument/publishDiagnostics
Returns a PublishDiagnostic object