Copy files or folders. Implementing this function is optional but it will speedup the copy operation.
The existing file.
The destination location.
Defines if existing files should be overwritten.
Create a new directory (Note, that new files are created via write
-calls).
The uri of the new folder.
Delete a file.
The resource that is to be deleted.
Defines if deletion of folders is recursive.
Read the entire contents of a file.
The uri of the file.
An array of bytes or a thenable that resolves to such.
Retrieve metadata about a file.
Note that the metadata for symbolic links should be the metadata of the file they refer to.
Still, the SymbolicLink-type must be used in addition to the actual type, e.g.
FileType.SymbolicLink | FileType.Directory
.
The uri of the file to retrieve metadata about.
The file metadata about the file.
Subscribe to events in the file or folder denoted by uri
.
The editor will call this function for files and folders. In the latter case, the
options differ from defaults, e.g. what files/folders to exclude from watching
and if subfolders, sub-subfolder, etc. should be watched (recursive
).
The uri of the file to be watched.
Configures the watch.
A disposable that tells the provider to stop watching the uri
.
Write data to a file, replacing its entire contents.
The uri of the file.
The new content of the file.
Defines if missing files should or must be created.
An event to signal that a resource has been created, changed, or deleted. This event should fire for resources that are being watched by clients of this provider.
Note: It is important that the metadata of the file that changed provides an updated
mtime
that advanced from the previous value in the stat and a correctsize
value. Otherwise there may be optimizations in place that will not show the change in an editor for example.