Formatting rules to prevent false positives when merging pull requests

[jhoek]

When examining the differences introduced by a pull request, it's nice not to be distracted by false positives due to different code formatting styles (e.g. spaces around operators, placement of curly brackets, use of new line characters etc.) - relevant changes could easily be missed in a haystack of "noise".

Before working on any other pull requests, I would like to suggest the introduction of a workspace settings file containing the project's formatting rules. By putting this into the repo, all developers use the same rules (as workspace settings override user settings).

Note that this assumes that most people these days use VS Code to edit their PowerShell files.