Add .editorconfig and .gitattributes for consistent coding standards #139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This links with issue #138
To help ensure consistent coding standards and improve cross-platform collaboration, I propose adding the following files to the repository:
1
.editorconfig
– Helps enforce consistent indentation, line endings, charset, etc., across different editors and IDEs.2
.gitattributes
– Useful for defining how Git should handle line endings and text encoding, and for marking binary files.Benefits:
Prevents common formatting issues (e.g., mixed tabs/spaces, inconsistent line endings).
Simplifies collaboration by aligning developer environments automatically.
Reduces noise in diffs caused by inconsistent formatting.