There is no “leading” whitespace involved in this problem. The problem is just that vscode removes two trailing spaces. It does not remove any leading space otherwise your code would not be indented.
The current option called files.trimTrailingWhitespace, also trims ““leading”” whitespaces in files, which is the root cause of the problem. Because of that, you can’t have one or the other.
So, for this scenario, we still want to be able to trim leading whitespace in our files without affecting elixir markdown documentation.
The problem is not caused directly because of leading whitespace and this was never (in my perception) even suggested. It’s caused because of trailing whitespace being removed as well as leading whitespaces - because you only have one option to configure it and it does both.
Update:
To illustrate a little more:
You can clearly see that the current behavior considers all whitespace as ““trailing”” (hence the option). The editor doesn’t make the distinction between whitespace that goes before (leading) or after (trailing) content. Indentation would still be preserved, just not for “blank” lines.
Another example:
If whitespace were by default considered leading whitespace until there’s content, this file could be formatted without losing the markdown line breaks at the end. It would also be easier to remove blank lines after this.
