rust/crates/ra_lsp_server/src/lib.rs

mod caps;
mod cargo_target_spec;
mod conv;
mod main_loop;
mod markdown;
mod project_model;
mod vfs_filter;
pub mod req;
pub mod init;
mod server_world;

pub type Result<T> = ::std::result::Result<T, ::failure::Error>;
pub use crate::{caps::server_capabilities, main_loop::main_loop, main_loop::LspError, init::InitializationOptions};
split lib 2018-09-01 10:16:08 -05:00			`mod caps;`
Move `CargoTargetSpec` and friends to cargo_target_spec module 2019-01-12 12:00:58 -06:00			`mod cargo_target_spec;`
split lib 2018-09-01 10:16:08 -05:00			`mod conv;`
			`mod main_loop;`
Pass Documentation up to LSP and add "rust" to our codeblocks there 2019-01-29 20:39:09 -06:00			`mod markdown;`
introduce project model 2018-09-02 03:37:16 -05:00			`mod project_model;`
Improve filtering of file roots `ProjectWorkspace::to_roots` now returns a new `ProjectRoot` which contains information regarding whether or not the given path is part of the current workspace or an external dependency. This information can then be used in `ra_batch` and `ra_lsp_server` to implement more advanced filtering. This allows us to filter some unnecessary folders from external dependencies such as tests, examples and benches. 2019-03-19 08:14:16 -05:00			`mod vfs_filter;`
Cargo Format Run `cargo fmt` and ignore generated files 2018-10-15 16:44:23 -05:00			`pub mod req;`
Add showWorkspaceLoadedNotification to vscode client This allows users to control whether or not they want to see the "workspace loaded" notification. This is done on the server side using InitializationOptions which are provided by the client. By default show_workspace_loaded is true, meaning the notification is sent. 2019-03-06 03:34:38 -06:00			`pub mod init;`
Cargo Format Run `cargo fmt` and ignore generated files 2018-10-15 16:44:23 -05:00			`mod server_world;`
split lib 2018-09-01 10:16:08 -05:00
			`pub type Result<T> = ::std::result::Result<T, ::failure::Error>;`
Add showWorkspaceLoadedNotification to vscode client This allows users to control whether or not they want to see the "workspace loaded" notification. This is done on the server side using InitializationOptions which are provided by the client. By default show_workspace_loaded is true, meaning the notification is sent. 2019-03-06 03:34:38 -06:00			`pub use crate::{caps::server_capabilities, main_loop::main_loop, main_loop::LspError, init::InitializationOptions};`