-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Install extensions without restarting the editor #5675
Comments
There are some things that are easy and some things that are not :). All the extension point handlers are (through API shape) forced to be written as listeners, so all of them would correctly get a "late to the party" extension description. So from an infrastructure point of view, we would need to ping all extension hosts and renderers processes from the shared process that manages extensions and inform everybody there is a new extension available. What I cannot tell is if we have places where we cache things or where we make decisions that cannot be revisited. For example, if a "late to the party" extension contributes a new language (for file extensions .alex), if you open a file before the extension is installed it stays open in the Perhaps we should just turn this on from the infrastructure side and deal with the bugs on a case by case basis. Possible issues: in the users of |
I believe this was added in 1.31: https://code.visualstudio.com/updates/v1_31#_no-reload-on-install |
I searched on the issue tracker and I wasn’t able to find an open discussion on this feature improvement. So here it is, the idea would be to remove the “Restart Code” step that we have to do after the installation of a new extension and which breaks the workflow (for instance if you have unsaved files you need to make a decision on them) and isn’t applied on every Code instances (cf. #3268).
I understand that from a technical point of view, it is easier to restart the editor if its code base changed because of a new extension. However it should still be possible to implement some dynamic extension loading with the correct abstractions and some engineering effort. So I would be happy if this issue could host the discussion on the technical challenges involved and the willingness to make dynamic loading happen.
The text was updated successfully, but these errors were encountered: