-
Notifications
You must be signed in to change notification settings - Fork 32k
Fix dirty setting update logic #58926
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
Fix dirty setting update logic #58926
Conversation
* Dirty setting will update when focused with a higher debounce * Dirty setting will immediately update when blurred
I'm not sure, I liked the comment that only text setting updates should have a slow debounce, and other types should be committed as fast as possible. What do you think? Should we send the type with onDidChangeSetting, and debounce differently based on the type? |
* Added a new enum for setting types * Added separate `Delayer` with a long debounce for non-text inputs
@roblourens Updated :) |
src/vs/workbench/services/preferences/common/preferencesModels.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!!
@roblourens Just making sure - CI build for latest commit says unit tests are failing on Linux, but it seems that the problem is not with my changes. Is it OK? |
Yeah I checked it out and it looked like a flaky test 👍 |
This PR closes #58537.
Setting that are dirty will now update: