Skip to content

Make file watching an optional client capability #237

@mickaelistria

Description

@mickaelistria

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.

Cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=516216

Metadata

Metadata

Assignees

No one assigned

    Labels

    *out-of-scopePosted issue is not in scope of VS Codefeature-requestRequest for new features or functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions