Compare changes of ExtensionConfiguration object and call extensionController.configurationChanged only when ExtensionConfiguration is updated.
This change includes a refactor of ExtensionConfiguration.
Why
VS Code's ConfigurationChangeEvent is triggered every time when the configuration of workspace updates.
This may cause the unintentional extension restart, for example: workbench.action.zoomIn triggers this kind of event and the extension restarts when executed by a button-press.
Restarts of the extension is necessary when the configuration of the extension, thus this change compares a change of ExtensionConfiguration and trigger restarts only when the extension configuration is updated.
What I changed
Compare changes of ExtensionConfiguration object and call
extensionController.configurationChangedonly when ExtensionConfiguration is updated.This change includes a refactor of ExtensionConfiguration.
Why
VS Code's ConfigurationChangeEvent is triggered every time when the configuration of workspace updates.
This may cause the unintentional extension restart, for example:
workbench.action.zoomIntriggers this kind of event and the extension restarts when executed by a button-press.Restarts of the extension is necessary when the configuration of the extension, thus this change compares a change of ExtensionConfiguration and trigger restarts only when the extension configuration is updated.
Related issues
fixes https://github.com/nicollasricas/vscode-deck/issues/36