Documentation

FailureHandlingKind
in package

AbstractYes

Defines how the host (editor) should sync document changes to the language server.

Table of Contents

Constants

ABORT  = 'abort'
Applying the workspace change is simply aborted if one of the changes provided fails. All operations executed before the failing operation stay executed.
TEXT_ONLY_TRANSACTIONAL  = '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.
TRANSACTIONAL  = 'transactional'
All operations are executed transactional. That means they either all succeed or no changes at all are applied to the workspace.
UNDO  = 'undo'
The client tries to undo the operations already executed. But there is no guarantee that this is succeeding.

Constants

ABORT

Applying the workspace change is simply aborted if one of the changes provided fails. All operations executed before the failing operation stay executed.

public mixed ABORT = 'abort'

TEXT_ONLY_TRANSACTIONAL

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.

public mixed TEXT_ONLY_TRANSACTIONAL = 'textOnlyTransactional'

TRANSACTIONAL

All operations are executed transactional. That means they either all succeed or no changes at all are applied to the workspace.

public mixed TRANSACTIONAL = 'transactional'

UNDO

The client tries to undo the operations already executed. But there is no guarantee that this is succeeding.

public mixed UNDO = 'undo' 

        

        
    




    

    

                                

                

                                
    

        On this page

        
    


                

                            

            

    

        

            
Search results