Table of Contents

Class DidRenameWorkspaceFilesParams

Namespace
RDCore.SDK.Platform.Protocol
Assembly
RDCore.SDK.dll

workspace/didRenameFiles (LSP 3.17 §Workspace, DidRenameFiles Notification): a client renamed or moved files or folders.

[Serial]
[Method("workspace/didRenameFiles", Direction.ClientToServer)]
public sealed record DidRenameWorkspaceFilesParams : IRequest, IRequest<Unit>, IBaseRequest, IEquatable<DidRenameWorkspaceFilesParams>
Inheritance
DidRenameWorkspaceFilesParams
Implements
IRequest
IRequest<Unit>
IBaseRequest
Inherited Members

Remarks

OmniSharp 0.19.9 reads the notification as DidRenameFileParams, whose FileRename has only a uri: the oldUri and newUri a client sends are not read, and every rename is one from nowhere to nowhere. This is the same notification, read as the protocol states it. A server that handles it says so in its initialize result itself (workspace.fileOperations.didRename), since no OmniSharp handler registers it. The notification is serial: OmniSharp reads a serial message after every message before it is done, and the ones after it once it is. A client sends textDocument/didClose for the old path and didOpen for the new one before it says the files were renamed, and a server that reads the rename beside them sees a document open at a path before it has moved there. The group of parallel messages before a serial one is done before it is read, so the rename is made after the close and before the notifications that follow it.

Properties

Files

The files and folders that were renamed, in the order the client renamed them.

[JsonProperty("files")]
public WorkspaceFileRename[] Files { get; init; }

Property Value

WorkspaceFileRename[]