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
This bug is a follow up to ongoing work on #7105. When a preference file is open in the editor, changes in the GUI are written to the file, but the file is not saved. In VSCode, if the file is not dirty when a preference change is made in the GUI, the file is automatically saved.
Open the preferences file corresponding to your current scope (e.g. by clicking the {} in the upper right.)
Modify preferences in the GUI
Observe that the preferences changes are not registered by the GUI (no blue bars appear), that the file is marked as dirty, and that the preference changes are written to it, but not saved.
Additional Information
The current behavior is governed by a call to applyBackgroundEdit here:
Bug Description:
This bug is a follow up to ongoing work on #7105. When a preference file is open in the editor, changes in the GUI are written to the file, but the file is not saved. In VSCode, if the file is not dirty when a preference change is made in the GUI, the file is automatically saved.
Steps to Reproduce:
{}
in the upper right.)Additional Information
The current behavior is governed by a call to
applyBackgroundEdit
here:theia/packages/preferences/src/browser/abstract-resource-preference-provider.ts
Line 154 in 9286ffe
That method explicitly does not save the file if the editor is open.
The text was updated successfully, but these errors were encountered: