FailureHandlingKind (org.eclipse.lsp4j 0.24.0 API)

java.lang.Object
- org.eclipse.lsp4j.FailureHandlingKind

public final class FailureHandlingKind
extends java.lang.Object

The kind of failure handling supported by the client.

Since 3.13.0

Field Summary

Fields
Modifier and Type	Field	Description
`static java.lang.String`	`Abort`	Applying the workspace change is simply aborted if one of the changes provided fails.
`static java.lang.String`	`TextOnlyTransactional`	If the workspace edit contains only textual file changes they are executed transactional.
`static java.lang.String`	`Transactional`	All operations are executed transactional.
`static java.lang.String`	`Undo`	The client tries to undo the operations already executed.

Method Summary
- Methods inherited from class java.lang.Object
  clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Field Detail
  - Abort
```
public static final java.lang.String Abort
```
    Applying the workspace change is simply aborted if one of the changes provided fails. All operations executed before the failing operation stay executed.
    
    See Also:
    
    Constant Field Values
  - Transactional
```
public static final java.lang.String Transactional
```
    All operations are executed transactional. That means they either all succeed or no changes at all are applied to the workspace.
    
    See Also:
    
    Constant Field Values
  - TextOnlyTransactional
```
public static final java.lang.String TextOnlyTransactional
```
    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.
    
    See Also:
    
    Constant Field Values
  - Undo
```
public static final java.lang.String Undo
```
    The client tries to undo the operations already executed. But there is no guarantee that this is succeeding.
    
    See Also:
    
    Constant Field Values