Aligning formatting across files

[egekorkan]

Similar to binding templates repository, we can add an editorconfig file so that :

• The documents we need to edit the source code of is easier to do and we avoid unwanted whitespace changes.
• Some documents like JSON Schema can be also read by developers so we should provide a "nice looking" document to them.
• We have a convention on when to do line breaks. Having multiple sentences in one line is annoying for git diffs, which makes reviewing, and suggesting difficult.

I would exclude files that are auto-generated and also all the existing HTML files in the publication folder.

[egekorkan]

Call of 20.12:

• We should also use a format in the CI pipeline to fix such misformating when somebody edits via GitHub or editor without editorconfig support.
• We can use Prettier instead of editorconfig but it may not work in IDEs other than VS Code.
  • https://prettier.io/docs/en/configuration.html#editorconfig can be used to make Prettier use editorconfig file.
• We should hook it up to husky
• There will be no impact for reviewers since we use HTML diff anyways
• We can start with editorconfig, check it works and then use Prettier on top.
• Spaces for indentation, UNIX ending (since W3C server is unix-based).
• We should add gitattribute so that the first clone is using the correct line ending.

[egekorkan]

After trying to get prettier to work with editorconfig, I have found prettier/prettier#15255 (comment) which says that prettier will always read the editorconfig file but it does not really take the excluded parts into account. So I propose to maintain two configurations but keep them consistent.