ReadonlycapabilitiesThe FileSystemProviderCapabilities for this provider.
ReadonlyonReadonlyonEvent that is fired if a (watched) file in the filesystem of this provider has changed.
Protected ReadonlyonReadonlyonEvent that is fired if an error occurred when watching files in the filesystem of this provider.
Delete the given resource.
The URI of the resource to delete.
Options to define if files should be deleted recursively and if the trash should be used.
ProtectedfetchCreate a new directory using the given resource uri.
The URI of the new folder.
Optional function that has to be implemented by FileSystemProviderWithFileReadWriteCapability. See FileSystemProviderWithFileReadWriteCapability#readFile for additional documentation.
Rename a file or folder.
URI of the existing file or folder.
URI of the target location.
Options to define if existing files should be overwritten.
ProtectedtoMaps the URI back to the path the build actually wrote, built through Endpoint so this
still works when the application is deployed under a sub-path. URI.path is decoded, so it
has to be re-encoded - otherwise a # or ? in an asset name would be read as a fragment or
query.
Watch the given resource and react to changes by firing the FileSystemProvider#onDidChangeFile event.
URI of the resource to be watched.
Options to define if the resource should be watched recursively and to provide a set of resources that should be excluded from watching.
A Disposable that can be invoked to stop watching the resource.
Optional function that has to be implemented by FileSystemProviderWithFileReadWriteCapability. See FileSystemProviderWithFileReadWriteCapability#writeFile for additional documentation.
Reads the plugin assets the build dropped under
PLUGINS_BASE_PATH. With a backend those come off its disk viafile:; browser-only has to fetch them over HTTP.Read-only, and only for what goes through the
FileService: color themes, icon themes, icon fonts.