-
Notifications
You must be signed in to change notification settings - Fork 944
Make file watching an optional client capability #237
Copy link
Copy link
Closed
Labels
*out-of-scopePosted issue is not in scope of VS CodePosted issue is not in scope of VS Codefeature-requestRequest for new features or functionalityRequest for new features or functionality
Description
I have the impression that the didChangeWatchedFile notification is too much. Why do we need it when we already have didChange/didSave? It seems simple to send a didChange and/or a didSave for a file (even if it wasn't open first) when we see a change. What makes the watches files so special?
Overall, I think this operation is too much, and the real issue when trying to consume watched files is more to be informed from the server about which files to watch.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
*out-of-scopePosted issue is not in scope of VS CodePosted issue is not in scope of VS Codefeature-requestRequest for new features or functionalityRequest for new features or functionality