aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_lsp_server
Commit message (Collapse)AuthorAgeFilesLines
...
* make CTX type param instead of assoc typeAleksey Kladov2019-08-201-34/+25
| | | | that way, we can implement ConvWith<&'_ CTX> for different lifetimes
* add tests for crlfAleksey Kladov2019-08-201-0/+46
|
* minorAleksey Kladov2019-08-201-1/+1
|
* don't load sysroot in most heavy testsAleksey Kladov2019-08-195-12/+33
|
* update lspAleksey Kladov2019-08-173-6/+2
|
* implement durabilityAleksey Kladov2019-08-151-0/+1
|
* Drop support for old extendSelection APIAleksey Kladov2019-08-123-44/+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-062-14/+2
|\ | | | | | | | | | | | | | | | | | | | | | | 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-042-14/+2
| |
* | fix testsAleksey Kladov2019-08-061-2/+2
| |
* | allow to exclude certain files and directoriesAleksey Kladov2019-08-063-14/+29
| |
* | rename configAleksey Kladov2019-08-064-19/+14
| |
* | introduce ra_vfs_glob crateAleksey Kladov2019-08-064-59/+17
| | | | | | | | It manages exclusion rules for the vfs crate
* | cleanupAleksey Kladov2019-08-062-2/+2
| |
* | renameAleksey Kladov2019-08-061-9/+9
| |
* | use Conv for severityAleksey Kladov2019-08-062-20/+21
| |
* | Add test for #1540Jeremy Kolb2019-08-031-0/+17
|/
* remove-commentkjeremy2019-07-311-1/+0
|
* Add explicit newline preserving testskjeremy2019-07-311-0/+6
|
* Fixed review commentsRoman Stoliar2019-07-301-3/+9
|
* Hide comments in rust section of doc commentsRoman Stoliar2019-07-303-5/+21
|
* Support destructuring patternsKirill Bulatov2019-07-282-0/+6
|
* Improve inlay hinting for typesKirill Bulatov2019-07-262-0/+4
| | | | | | Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code.
* Make Analysis api cancellableKirill Bulatov2019-07-253-37/+48
|
* Merge #1549bors[bot]2019-07-233-1/+50
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1549: Show type lenses for the resolved let bindings r=matklad a=SomeoneToIgnore Types that are fully unresolved are not displayed: <img width="279" alt="image" src="https://user-images.githubusercontent.com/2690773/61518122-8e4ba980-aa11-11e9-9249-6d9f9b202e6a.png"> A few concerns that I have about the current implementation: * I've adjusted the `file_structure` API method to return the information about the `let` bindings. Although it works fine, I have a feeling that adding a new API method would be the better way. But this requires some prior discussion, so I've decided to go for an easy way with an MVP. Would be nice to hear your suggestions. * There's a hardcoded `{undersolved}` check that I was forced to use, since the method that resolves types returns a `String`. Is there a better typed API I can use? This will help, for instance, to add an action to the type lenses that will allow us to navigate to the type. Co-authored-by: Kirill Bulatov <[email protected]>
| * Code review fixesKirill Bulatov2019-07-223-1/+50
| |
| * 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
| |
* | flexi_logger 0.14kjeremy2019-07-221-1/+1
|/
* Add "Run" lens for binary runnablesKirill Bulatov2019-07-161-1/+1
|
* cargo updatekjeremy2019-07-151-1/+1
|
* Remove executeCommandProvider: apply_code_action.Michael Bolin2019-07-112-10/+8
| | | | | | | | | | | | | | | | | | | This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it.
* Ignore workspace/didChangeConfiguration notifications.Michael Bolin2019-07-112-4/+11
|
* Remove unused dependenciesShotaro Yamada2019-07-081-1/+0
|
* don't send LocationLink unless the client opts-inAleksey Kladov2019-07-085-12/+62
| | | | closes #1474
* simplifyAleksey Kladov2019-07-082-23/+20
|
* add try_conv_with_to_vecAleksey Kladov2019-07-082-40/+54
|
* Simplify responses by using into()Jeremy Kolb2019-07-072-12/+13
|
* use flatten branch of lsp-typesJeremy Kolb2019-07-073-26/+17
|
* Formatting againJeremy Kolb2019-07-051-5/+5
|
* Symplify by using into()Jeremy Kolb2019-07-051-3/+3
|
* FormattingJeremy Kolb2019-07-041-1/+3
|
* Some clippy fixes for 1.36Jeremy Kolb2019-07-042-5/+4
|
* Fix formattingJeremy Kolb2019-07-041-5/+5
|
* Change default()Jeremy Kolb2019-07-041-1/+1
|