You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, while an attempt has been made to reload the vscode configs, it doesn't actually work.
While the detection by onDidChangeConfiguration properly triggers the event, my attempt reloading the config with vscode.workspace.getConfiguration doesn't read in the newer configs.
Is there a way to fix this? If not, we need to create a warning/notice for users to reload.
The text was updated successfully, but these errors were encountered:
Mysterious forces are in play, failing to reproduce this... The current loadConfig should be working in most cases at least.
Worst case, we will need to add lines to either restart the extension host vscode.commands.executeCommand('workbench.action.restartExtensionHost');, or reload the window vscode.commands.executeCommand('workbench.action.reloadWindow');. Both will have performance implications and potentially cause issues when working with a remote ssh vscode session.
This bug might only trigger when the autobackup is enabled. We'll tackle this again after #20 is fixed.
Currently, while an attempt has been made to reload the vscode configs, it doesn't actually work.
While the detection by
onDidChangeConfiguration
properly triggers the event, my attempt reloading the config withvscode.workspace.getConfiguration
doesn't read in the newer configs.Is there a way to fix this? If not, we need to create a warning/notice for users to reload.
The text was updated successfully, but these errors were encountered: