Instead of going to the backend with each file URI to ask whether it can handle the current file or not,
we have this map of extension and priority pairs that we populate at application startup.
The real advantage of this approach is the following: Phosphor cannot run async code when invoking isEnabled/isVisible
for the command handlers
so the menu item would be always visible for the user even if the file type cannot be handled eventually.
Hopefully, we could get rid of this hack once we have migrated the existing Phosphor code to React.
Instead of going to the backend with each file URI to ask whether it can handle the current file or not, we have this map of extension and priority pairs that we populate at application startup. The real advantage of this approach is the following: Phosphor cannot run async code when invoking
isEnabled/isVisiblefor the command handlers so the menu item would be always visible for the user even if the file type cannot be handled eventually. Hopefully, we could get rid of this hack once we have migrated the existing Phosphor code to React.