Vscode: Option to disable "Failed to save '...': The content on disk is newer." check

[egonelbre]

I would like an option to disable dirty write checking:

Failed to save 'xyz': The content on disk is newer. Please compare your version with the one on disk.

My workflow does include dirty writes and having to go through the merging is annoying.

Example: keeping dirty state in an open file then switching git branch to save and commit (that file only), then switching back to the previous branch.

[MBurtsev]

I am too.

[brianonn]

I saw this for the first time today, there is no option to "Force save anyways, because I know better than my IDE"

I know I can click on the [Compare] button and then click the checkmark in the diff view to save my file, but sometimes I just know I want to save without looking at a diff. The dialog should have a [Force Save] button too.

[donnie-msft]

I seem to recall that VSCode used to refresh the file contents more often.

Also, if I make another edit to the file in VSCode, I'd expect that I would now "win" the race and my save would occur, but instead I'm stuck with "failed to save" errors.

Even closing and reopening VSCode doesn't affect this. I have to close the file, say "don't save", then reopen the file to be able to make edits. Feels like a design change or regression?

[bpasero]

Pushed 2 changes to make this better:

• a new setting files.saveConflictResolution that allows to turn off save conflict detection (this can be set on a folder level so that e.g. you can disable this selectively for network folders only)
• a way to overwrite a file directly from the notification selectively

[bpasero]

Note: setting name changed to files.saveConflictResolution and needs to be configured as overwriteFileOnDisk to disable the confirmation prompt.