Related to #63, add a platform-agnostic way of ensuring two-spaces/line endings/encoding in all files.
Why are we doing this?
Help ensure standard file formatting.
Benefits
It will make life easier for contributors who have their editor configured in different ways than how Piotr has specified.
Drawbacks
[*] could be too greedy, but I didn't immediately see any other file types that should have a different tab/encoding/etc style.
Requirements
Put an X between brackets on each line if you have done the item:
[n/a] Tests written & passing locally?
[x] Code style checked?
[x] Rebased with master branch?
[x] Documentaion updated?
piotrmurach
commented
4 years ago
Describe the change
Related to #63, add a platform-agnostic way of ensuring two-spaces/line endings/encoding in all files.
Why are we doing this?
Help ensure standard file formatting.
Benefits
It will make life easier for contributors who have their editor configured in different ways than how Piotr has specified.
Drawbacks
[*]could be too greedy, but I didn't immediately see any other file types that should have a different tab/encoding/etc style.Requirements
Put an X between brackets on each line if you have done the item: [n/a] Tests written & passing locally? [x] Code style checked? [x] Rebased with
masterbranch? [x] Documentaion updated?