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

Provide more granular file change events based on VS Code file create/delete events #1805

Merged
merged 7 commits into from
Oct 27, 2017

Conversation

rchande
Copy link

@rchande rchande commented Oct 24, 2017

…/delete events

@DustinCampbell DustinCampbell changed the title Provide more granular file change events based on VS Code file create… Provide more granular file change events based on VS Code file create/delete events Oct 24, 2017
Copy link
Member

@DustinCampbell DustinCampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Except, I think the property name in the protocol is incorrect.

let d1 = watcher.onDidCreate(onFileSystemEvent(FileChangeType.Create));
// In theory we don't need to subscribe to "change" notifications
// because we already get them through the buffer update request
//let d2 = watcher.onDidChange(onFileChange);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe move this to be last so that there isn't a gap between d1 and d3?

@@ -417,6 +417,17 @@ export interface PackageDependency {
Name: string;
Version: string;
}

export interface FilesChangedRequest extends Request{
ChangeType: FileChangeType
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You called this FileChangeType in your omnisharp-roslyn PR. So this probably doesn't actually work. 😄

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the member name in the other PR.

Copy link
Member

@DustinCampbell DustinCampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I'll wait until we update to a new OmniSharp release before merging.

@DustinCampbell
Copy link
Member

@rchande: Out of curiosity, have you tested that this works? I'm curious since the protocol didn't match omnisharp-roslyn at first.

@rchande
Copy link
Author

rchande commented Oct 25, 2017

@DustinCampbell I did test this--verified in the debugger that we were getting hit for both create and delete events.

@rchande rchande merged commit 5f655e9 into dotnet:master Oct 27, 2017
@rchande rchande deleted the fileChangeNotification branch October 27, 2017 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants