Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement DidCloseTextDocument LSP handler #53

Open
retailcoder opened this issue Mar 12, 2023 · 0 comments
Open

Implement DidCloseTextDocument LSP handler #53

retailcoder opened this issue Mar 12, 2023 · 0 comments
Labels
component: Server.LSP Issue involves the LSP server process

Comments

@retailcoder
Copy link
Member

Specification (LSP)

The document close notification is sent from the client to the server when the document got closed in the client. The document’s master now exists where the document’s Uri points to (e.g. if the document’s Uri is a file Uri the master now exists on disk). As with the open notification the close notification is about managing the document’s content. Receiving a close notification doesn’t mean that the document was open in an editor before. A close notification requires a previous open notification to be sent. Note that a server’s ability to fulfill requests is independent of whether a text document is open or closed.

The server should update its internal document state upon receiving this notification, and write log entries as appropriate.

@retailcoder retailcoder added component: Server.LSP Issue involves the LSP server process component: Rubberduck.Client Issue involves RPC client/platform and removed component: Rubberduck.Client Issue involves RPC client/platform labels Mar 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: Server.LSP Issue involves the LSP server process
Projects
None yet
Development

No branches or pull requests

1 participant