Followup to #12 , discussions made there and there.
A developer can register a callback that happens when an executeCommand is fired for DoBlaBlaJavaThingyTypeBeat. If a command was not registered with a callback by the developer - let that Command reach the server. Otherwise - fire the callback that was registered by the developer.
This brings package developers full control as to how Commands are executed "globally".
i.e - they can register a command and a callback for it, and have parts of their package (like code actions, or other custom areas) call those Commands and have them executed just like VSCode does today. But, this will probably be mainly needed/used for code actions, where the standard isn't explicit with Commands are executed.
I could also use some help testing this with ide-java as I'm not used to building and debugging extensions. I can do this myself but if anyone can easily test this let me know.
Followup to #12 , discussions made there and there.
A developer can register a callback that happens when an
executeCommand
is fired forDoBlaBlaJavaThingyTypeBeat
. If a command was not registered with a callback by the developer - let thatCommand
reach the server. Otherwise - fire the callback that was registered by the developer.This brings package developers full control as to how
Command
s are executed "globally". i.e - they can register a command and a callback for it, and have parts of their package (like code actions, or other custom areas) call thoseCommand
s and have them executed just like VSCode does today. But, this will probably be mainly needed/used for code actions, where the standard isn't explicit withCommand
s are executed.I could also use some help testing this with ide-java as I'm not used to building and debugging extensions. I can do this myself but if anyone can easily test this let me know.
@UziTech