This configures VS to save files with a certain amount of consistency. I haven't decided to make it use any specific indentation style, but we could settle on tabs with tab-width=4. Which seems to be the default anyway.
Adding this config gives us some control over accidentally making unnecessary changes. I.e., it helps keep git history clean. VS likes to let the user add trailing whitespace for no reason at all, and these lines end up getting changed by unrelated edits when someone else saves with trim-trailing-whitespace enabled.
The UTF-8 encoding is the most important setting, because GitHub does not support rendering UTF-16 (Windows default "Unicode" encoding) in the web app.
There will be some amount of churn as all files are normalized to the new settings over time. It could be done in one push, but I've decided not to for now, just to keep this PR small and easy to review.
This configures VS to save files with a certain amount of consistency. I haven't decided to make it use any specific indentation style, but we could settle on tabs with tab-width=4. Which seems to be the default anyway.
Adding this config gives us some control over accidentally making unnecessary changes. I.e., it helps keep git history clean. VS likes to let the user add trailing whitespace for no reason at all, and these lines end up getting changed by unrelated edits when someone else saves with trim-trailing-whitespace enabled.
The UTF-8 encoding is the most important setting, because GitHub does not support rendering UTF-16 (Windows default "Unicode" encoding) in the web app.
There will be some amount of churn as all files are normalized to the new settings over time. It could be done in one push, but I've decided not to for now, just to keep this PR small and easy to review.