Skip to content

Fixes FailureHandlingKind after LSP spec update #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
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
18 changes: 13 additions & 5 deletions src/Protocol/Models/FailureHandlingKind.cs
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,8 @@ namespace OmniSharp.Extensions.LanguageServer.Protocol.Models
public enum FailureHandlingKind
{
/// <summary>
/// All operations are executed transactional. That means they either all
/// succeed or no changes at all are applied to the workspace.
/// Applying the workspace change is simply aborted if one of the changes provided
/// fails. All operations executed before the failing operation stay executed.
/// </summary>
[EnumMember(Value = "abort")]
Abort,
Expand All @@ -20,9 +20,17 @@ public enum FailureHandlingKind
[EnumMember(Value = "transactional")]
Transactional,
/// <summary>
///Supports deleting existing files and folders.
/// If the workspace edit contains only textual file changes they are executed transactional.
/// If resource changes (create, rename or delete file) are part of the change the failure
/// handling strategy is abort.
/// </summary>
[EnumMember(Value = "textOnlyTransactional")]
TextOnlyTransactional,
/// <summary>
/// The client tries to undo the operations already executed. But there is no
/// guarantee that this is succeeding.
/// </summary>
[EnumMember(Value = "delete")]
Delete,
[EnumMember(Value = "undo")]
Undo,
}
}