-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
Content is newer on disk should have overwrite call to action. UX issue #31063
Comments
@nojvek the actions for overwriting or taking the change are in the editor toolbar here: We can revisit to make them more prominent somehow. |
Btw you should never get this error when changing a setting. @sandy081 is working on improving this flow a lot. |
I thought I'd +1 this, rather than start a new issue. I sometimes get this error. In the little popup I want it to offer more than just the "Compare" button. I want a "Just Save It" button. (Or, it could be called "Overwrite Anyway". I don't want to mess around doing diffs, and having to work out what has changed and which is the correct version. I know that the version in the editor is the code I want on disk. (In my case it is because I forgot to save before I ran tests, and they have a side-effect of automatically fixing whitespace and similar issues.) To be clear: I do want the popup to tell me the file on disk is newer. I just want a quick way to tell it I know what I'm doing. |
Merging into #46706 |
I change my theme and I see this:
Its already on the compare screen so the CTA is meaningless.
So I click compare and I see the info box.
I type "ctrl+s" and go back to compare.
The appropriate call to actions are just present me with "Overwrite, undo, Cancel".
I searched help for overwrite and it doesn't even exist in edit menu.
My solution was to just close vscode and make the change myself after a restart. That is a terrible work around but it got the job done.
The text was updated successfully, but these errors were encountered: