You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, it'd be neat to allow programmatic registration of ICommands.
We have an extension which needs to do some file watching and rather than basically rewriting what you have here from scratch we'd like to do something like the following:
// code in activate() of our extensionletwatcher=extensions.getExtension('filewatcher').exports;// also possibly activate the ext herewatcher.register({"match": "*.foo","isAsync": true,"cmd": "echo '${file} bar'","event": "onFileChange"})
I haven't fully thought through how to show to the user what commands were registered this way. I guess there are multiple options - e.g. have some read-only view which would expose these, or dump these to some config file directly (probably not the user config).
Is this something you'd consider having in your extension? I'd be willing to contribute the patch if you agre to go through with this idea
The text was updated successfully, but these errors were encountered:
Hi, it'd be neat to allow programmatic registration of
ICommand
s.We have an extension which needs to do some file watching and rather than basically rewriting what you have here from scratch we'd like to do something like the following:
I haven't fully thought through how to show to the user what commands were registered this way. I guess there are multiple options - e.g. have some read-only view which would expose these, or dump these to some config file directly (probably not the user config).
Is this something you'd consider having in your extension? I'd be willing to contribute the patch if you agre to go through with this idea
The text was updated successfully, but these errors were encountered: