/cc @weinand This is for the debug scenario.

/cc @isidorn

@jrieken @weinand what is the scenario in debug where this is relevant. e.g. if we keep doing mkdirp for any file:// operation as before, what is the issue from that behaviour?

And who would set mkdirp to false currently or where would we want to add it?

@bpasero for debug there is no issue. The problem is that debug was relying on "mkdirp" when creating ".vscode/launch.json". But the remote filesystem provider doesn't use "mkdirp", so our code was failing there.
So if we have to implement a fallback strategy anyway, there is no point in supporting "mkdirp" for some filesystems but not for all.

set mkdirp to false currently or where would we want to add it?

You wanna set it to true, e.g when creating files but IMO it is not needed when saving a files that you have just opened.

@jrieken I think that depends. the file you have opened could have been deleted (including its parent folders) and our current behaviour is to restore the full path and file when you save it. Otherwise the behaviour would be weird:

• make a file dirty
• delete it on disk and its parent folders
• save it

=> you would get an error if mkdirp was set to false

We now do that...