about summary refs log tree commit diff
path: root/crates/rust-analyzer/src/handlers.rs
AgeCommit message (Collapse)AuthorLines
2022-07-19Work around Code bug with empty diagnosticsLaurențiu Nicola-1/+2
2022-07-11Fix obsolete `enableRangeFormatting` configTonalidadeHidrica-1/+1
2022-06-15fix: Clear proc-macro changed flag when reloading workspaceLukas Wirth-0/+1
2022-05-30Use char for trigger characterLukas Wirth-3/+4
2022-05-30fix: visibility completionyue4u-17/+16
2022-05-25internal: Make autoclosing angle brackets configurable, disabled by defaultLukas Wirth-1/+2
2022-05-22internal: Allow OnTypeFormatting to send SnippetTextEditFelicián Németh-3/+3
But continue to send TextEdit only.
2022-05-19internal: Improve inlay hint tooltipsLukas Wirth-6/+1
2022-05-17Allow inlay hint tooltips to trigger hoversLukas Wirth-36/+24
2022-05-17Trigger hover requests on closing brace hintsLukas Wirth-7/+49
2022-05-17feat: Implement inlay hint tooltipsLukas Wirth-0/+13
2022-05-01Initial config revampLukas Wirth-3/+3
2022-04-24Fix Reload Workspace commandEdwin Cheng-0/+7
2022-04-19Allows triggering commands after an assist editJonas Schievink-2/+3
2022-04-08Switch to LSP inlay hintsLaurențiu Nicola-27/+20
2022-04-03Merge #10802bors[bot]-7/+7
10802: Allow clients to configure the global workspace search limit r=Veykril a=knutwalker Playing around with [helix](https://helix-editor.com) I realized that the global worksapce symbol search works different compared to vs-code. Helix requires all possible symbols in one query and does no subsequent refinement searched. This PR adds a configuration option to override the default search limit with the default being the currently hardocded value. Helix users can increment this limit for their instance with a config like ```toml [[language]] name = "rust" language-server = { command = "rust-analyzer" } [language.config] workspace = { symbol = { search = { limit = 65536 }}} ``` Other editors are not affected by this change. Co-authored-by: Paul Horn <dev@knutwalker.engineer>
2022-03-31Add "view file text" command to debug sync issuesJonas Schievink-0/+8
2022-03-18Rename call info to "signature help"Jonas Schievink-3/+2
It is no longer limited to just calls
2022-03-12fix clippy::map_flattenMatthias Krüger-1/+1
2022-03-11fix: Allow configuration of colons in inlay-hintsLukas Wirth-2/+3
2022-03-04Fix formattingLaurențiu Nicola-1/+5
2022-03-04Load hints for part of the file onlyKirill Bulatov-2/+9
2022-02-11Handle proc-macro functions as the proc-macro they resolve toLukas Wirth-3/+1
2022-01-03fix: don't panic on seeing an unexpected offsetDavid Hotham-16/+17
2022-01-02Avoid collect_vec from itertoolsLaurențiu Nicola-3/+2
2021-12-07internal: add "Shuffle Crate Graph" commandJonas Schievink-0/+5
2021-12-05Merge #10902bors[bot]-2/+7
10902: Handle multiple cargo check quick fix spans r=Veykril a=brandondong Resolves https://github.com/rust-analyzer/rust-analyzer/issues/10705. **Cause:** - For a cargo check diagnostic with multiple spans, only a single quick fix action would be created at the location of `spans[0]`. Additionally, the hover window details would only show the location of `spans[0]` next to the message. **Fix:** - Allow cargo check quick fix actions to be triggerable from multiple selection ranges. Specifically, if the selection intersects with any of the replacement spans, the quick fix action is shown. - No change in behavior for the hover window details. It's pretty minor and I think showing multiple locations next to the message may be more confusing anyways. Co-authored-by: Brandon <brandondong604@hotmail.com>
2021-12-04Handle multiple cargo check quick fix spansBrandon-2/+7
2021-11-18Allow clients to configure the global workspace search limitPaul Horn-7/+7
2021-10-29Fix Plaintext textDocument/hovervsrs-1/+6
2021-10-22Use array IntoIterLaurențiu Nicola-1/+1
2021-10-21Migrate to edition 2021Lukas Wirth-1/+0
2021-10-18Pull in new lsp-types for VS compatLaurențiu Nicola-4/+4
2021-10-16more clippy fixesMilo-5/+4
2021-10-14Merge #10434bors[bot]-5/+64
10434: Allow `Locate parent module` command in Cargo.toml r=Veykril a=rainy-me close #10355 Co-authored-by: rainy-me <github@rainy.me> Co-authored-by: rainy-me <github@yue.coffee>
2021-10-14Provide navigations to parent modulesrainy-me-17/+21
2021-10-07Fix: compare pkg via manifestrainy-me-16/+1
2021-10-05Merge #10447bors[bot]-0/+1
10447: Add enum variant references CodeLens. r=Veykril a=ericsampson Co-authored-by: Eric Sampson <esampson@eaze.com>
2021-10-05Merge #10458bors[bot]-2/+4
10458: feat: Implement custom user snippets r=Veykril a=Veykril ![Y24dX7fOWX](https://user-images.githubusercontent.com/3757771/136059454-ceccfc2c-2c90-46da-8ad1-bac9c2e83ec1.gif) Allows us to address the following issues: - `.arc / .rc / .pin, similar to .box?` https://github.com/rust-analyzer/rust-analyzer/issues/7033 - `Add unsafe snippet` https://github.com/rust-analyzer/rust-analyzer/issues/10392, would allow users to have this without the diagnostic) - `.ok() postfix snippet is annoying` https://github.com/rust-analyzer/rust-analyzer/issues/9636, allows us to get rid of the `ok` postfix and similar ones - `Postfix vec completion` https://github.com/rust-analyzer/rust-analyzer/issues/7773 cc https://github.com/rust-analyzer/rust-analyzer/issues/772 Zulipd discussion: https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/Custom.20Postfix.20snippets Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
2021-10-05Replace `if let` with `match` where appropriateAramis Razzaghipour-8/+6
2021-10-04Make multiple import edits work for completionsLukas Wirth-2/+4
2021-10-04Add enum variant references CodeLens.Eric Sampson-0/+1
2021-10-03Allow locate parent module action in cargo tomlrainy-me-5/+75
2021-10-02internal: untangle usages of ReferenceCategory somewhatAleksey Kladov-2/+2
Not everything that can be read or write is a reference, let's try to use more precise types.
2021-09-24Give rustfmt spawn error context.Nixon Enraght-Moony-2/+7
2021-09-17fix completion handler trying to seek outside of character boundaries.Dawer-10/+7
With this patch, in these examples ```rust fn main() { "⊞$0"; } ``` ```rust struct S { д$0 u8 } ``` entering ':' character in `$0` places shouldn't cause panics.
2021-09-04internal: deduplicateAleksey Kladov-26/+16
2021-09-04fix: don't panic if the client sends invalid requestAleksey Kladov-1/+4
2021-09-01fix: multi-token mapping aware find referencesJonas Schievink-13/+17
2021-08-30Merge #10079bors[bot]-2/+3
10079: internal: make upstream bug less annoying r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>