Skip to content
This repository was archived by the owner on Dec 29, 2022. It is now read-only.

Remove obsolete custom progress reporting LSP messages #1429

Merged
merged 1 commit into from
Apr 15, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 0 additions & 34 deletions rls/src/lsp_data.rs
Original file line number Diff line number Diff line change
Expand Up @@ -342,40 +342,6 @@ impl ClientCapabilities {
}
}

/* --------------- Custom JSON-RPC notifications -------------- */

/// Custom LSP notification sent to client indicating that the server is currently
/// processing data and may publish new diagnostics on `rustDocument/diagnosticsEnd`.
#[derive(Debug)]
pub enum DiagnosticsBegin {}

impl LSPNotification for DiagnosticsBegin {
type Params = ();
const METHOD: &'static str = "rustDocument/diagnosticsBegin";
}

/// Custom LSP notification sent to client indicating that data processing started
/// by a `rustDocument/diagnosticsBegin` has ended.
/// For each `diagnosticsBegin` message, there is a single `diagnosticsEnd` message.
/// This means that for multiple active `diagnosticsBegin` messages, there will
/// be sent multiple `diagnosticsEnd` notifications.
#[derive(Debug)]
pub enum DiagnosticsEnd {}

impl LSPNotification for DiagnosticsEnd {
type Params = ();
const METHOD: &'static str = "rustDocument/diagnosticsEnd";
}

/// Custom LSP notification sent to client indicating that a build process has begun.
#[derive(Debug)]
pub enum BeginBuild {}

impl LSPNotification for BeginBuild {
type Params = ();
const METHOD: &'static str = "rustDocument/beginBuild";
}

/* ---------- Temporary LSP type until window/progress proposal is done --------- */

// Notification from server to client for build progress.
Expand Down