VS Code sometimes does not fire the rootFolder affectsConfiguration event when the extension itself is the one who updates it via getRootFolderPath(), breaking the functionality to set the root to read-only. This can be circumvented by directly calling the update in getRootFolderPath().
VS Code sometimes does not fire the rootFolder
affectsConfigurationevent when the extension itself is the one who updates it viagetRootFolderPath(), breaking the functionality to set the root to read-only. This can be circumvented by directly calling the update ingetRootFolderPath().