Extension activation order and status #1241
-
We have learned the hard way that the order of actions while activating the extension matters. For example, you may loose some commands if you first subscribe views and then commands, while doing in reverse eventually delivers those commands to the view after the extension gets activated (not a great CX though, because the user clicks and nothing seems to be happening... Anyway... Is there any guidance on the order of the activation actions for a frictionless activation? Also, we were not able to find a way to tell if the extension is still activating or not (apart from setting our own context variable. Is there a way or should jump the variable hoop? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think it is an intended solution. For example, GitLens heavily uses context variables:
A related issue: microsoft/vscode/issues/10471 |
Beta Was this translation helpful? Give feedback.
I think it is an intended solution. For example, GitLens heavily uses context variables:
A related issue: microsoft/vscode/issues/10471