-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
No activations event for file events #86063
Comments
This needs to go into the textfileservice and(or?) the working copy service |
To clarify: is this about allowing an extension to get activated on the new text file events introduced? Similar to how we activate file system providers for example? |
Yes. |
@dbaeumer any thoughts on the naming for such an activation? I assume you would want just one activation for any file operation and not one per kind right?
Isn't this the right place? Right before we call
|
To ensure that it is not mistaken with file events one idea would be |
@dbaeumer so
Fires? |
Yes, I think one is enough. We don't need to distinguish between create, rename and delete. |
Wouldn't the existing |
@bpasero just checking: wouldn't you need to trigger the activation. I assume a delete does neither read nor write the file. |
@jrieken with your undo logic, you now read files before delete to support undo right? So I would expect an activation here. |
I take it back, any IO operation whatsoever will activate the file system provider: vscode/src/vs/workbench/services/extensions/common/abstractExtensionService.ts Lines 117 to 119 in d81f0e4
Via vscode/src/vs/platform/files/common/fileService.ts Lines 116 to 117 in bb3aaa7
|
Testing #85929
We should have activation events for the provided file events (e.g.
onWillRename
, ...)The text was updated successfully, but these errors were encountered: