aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server/src/main_loop
Commit message (Collapse)AuthorAgeFilesLines
* disable the new typing handler for `->`Aleksey Kladov2019-10-251-0/+9
| | | | It doesn't actually work with LSP
* insert space after `->`Aleksey Kladov2019-10-251-0/+1
|
* make typing infra slightly more extensibleAleksey Kladov2019-10-251-6/+2
|
* for highlighting, search only the current fileAleksey Kladov2019-10-241-3/+8
|
* add couple of profiling callsAleksey Kladov2019-10-231-0/+4
|
* fix highlightingEkaterina Babshukova2019-10-221-0/+1
|
* restructure a bitEkaterina Babshukova2019-10-221-1/+1
|
* make `handle_references` accept refs from other filesEkaterina Babshukova2019-10-221-4/+9
|
* fixup folding ranges for "lineFoldingOnly" clients #2033Alex Zatelepin2019-10-211-2/+8
|
* Added test for check doc strings in crates.Alexander Andreev2019-09-303-0/+6
| | | | #1856
* move fold conversino to conv.rsAleksey Kladov2019-09-191-32/+6
|
* fix typoAleksey Kladov2019-09-191-1/+1
|
* fix renaming of modulesAleksey Kladov2019-09-051-8/+6
|
* cleanup main loopAleksey Kladov2019-08-311-1/+1
|
* move lsp-server to a separate repositoryAleksey Kladov2019-08-302-10/+11
|
* translate \n -> \r\n on the way outAleksey Kladov2019-08-201-2/+4
|
* update lspAleksey Kladov2019-08-171-2/+1
|
* Drop support for old extendSelection APIAleksey Kladov2019-08-121-22/+1
| | | | | | Emacs now handles this via native LSP request https://github.com/emacs-lsp/lsp-mode/commit/dc86bbb227147aa8141e690ad5648fdbd2ebdb9f
* Always set the runnable nameKirill Bulatov2019-08-091-11/+11
|
* Extract common logicKirill Bulatov2019-08-091-55/+42
|
* Show backtraces in lens runnablesKirill Bulatov2019-08-091-1/+5
|
* Merge #1652bors[bot]2019-08-061-8/+1
|\ | | | | | | | | | | | | | | | | | | | | | | 1652: Improve type hints behavior r=matklad a=SomeoneToIgnore This PR fixed the following type hints issues: * Restructures the `InlayKind` enum contents based on the discussion here: https://github.com/rust-analyzer/rust-analyzer/pull/1606#issuecomment-515968055 * Races described in #1639 * Caches the latest decorations received for each file to show them the next time the file is opened (instead of a new server request) Co-authored-by: Kirill Bulatov <[email protected]>
| * Use proper inlay kindsKirill Bulatov2019-08-041-8/+1
| |
* | use Conv for severityAleksey Kladov2019-08-061-15/+6
|/
* remove-commentkjeremy2019-07-311-1/+0
|
* Hide comments in rust section of doc commentsRoman Stoliar2019-07-301-1/+1
|
* Support destructuring patternsKirill Bulatov2019-07-281-0/+3
|
* Improve inlay hinting for typesKirill Bulatov2019-07-261-0/+3
| | | | | | Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code.
* Make Analysis api cancellableKirill Bulatov2019-07-251-29/+35
|
* Code review fixesKirill Bulatov2019-07-221-1/+22
|
* Do not show the lens with type hintsKirill Bulatov2019-07-211-13/+4
|
* Resolve types on the serverKirill Bulatov2019-07-211-25/+10
|
* Refactor server apiKirill Bulatov2019-07-201-28/+42
|
* If possible, show type lenses for the let bindingsKirill Bulatov2019-07-201-16/+26
|
* Add "Run" lens for binary runnablesKirill Bulatov2019-07-161-1/+1
|
* simplifyAleksey Kladov2019-07-081-23/+7
|
* add try_conv_with_to_vecAleksey Kladov2019-07-081-19/+8
|
* Simplify responses by using into()Jeremy Kolb2019-07-071-11/+12
|
* use flatten branch of lsp-typesJeremy Kolb2019-07-071-23/+12
|
* Formatting againJeremy Kolb2019-07-051-5/+5
|
* Symplify by using into()Jeremy Kolb2019-07-051-3/+3
|
* Fix formattingJeremy Kolb2019-07-041-5/+5
|
* Change default()Jeremy Kolb2019-07-041-1/+1
|
* Update to lsp-types 0.58.0Jeremy Kolb2019-07-041-5/+5
|
* allow rustfmt to reorder importsAleksey Kladov2019-07-041-11/+10
| | | | | | This wasn't a right decision in the first place, the feature flag was broken in the last rustfmt release, and syntax highlighting of imports is more important anyway
* Swallow expected `rustfmt` errorsRyan Cumming2019-06-261-10/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | My workflow in Visual Studio Code + Rust Analyzer has become: 1. Make a change to Rust source code using all the analysis magic 2. Save the file to trigger `cargo watch`. I have format on save enabled for all file types so this also runs `rustfmt` 3. Fix any diagnostics that `cargo watch` finds Unfortunately if the Rust source has any syntax errors the act of saving will pop up a scary "command has failed" message and will switch to the "Output" tab to show the `rustfmt` error and exit code. I did a quick survey of what other Language Servers do in this case. Both the JSON and TypeScript servers will swallow the error and return success. This is consistent with how I remember my workflow in those languages. The syntax error will show up as a diagnostic so it should be clear why the file isn't formatting. I checked the `rustfmt` source code and while it does distinguish "parse errors" from "operational errors" internally they both result in exit status of 1. However, more catastrophic errors (missing `rustfmt`, SIGSEGV, etc) will return 127+ error codes which we can distinguish from a normal failure. This changes our handler to log an info message and feign success if `rustfmt` exits with status 1. Another option I considered was only swallowing the error if the formatting request came from format-on-save. However, the Language Server Protocol doesn't seem to distinguish those cases.
* renameAleksey Kladov2019-06-011-33/+33
|
* move completed requests to a separate fileAleksey Kladov2019-05-313-11/+81
|
* less noisy statusAleksey Kladov2019-05-291-1/+1
|
* add latest requests to status pageAleksey Kladov2019-05-291-2/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-11 21:53:21 +0000