Add .editorconfig for consistent editor settings - #72
Merged
Conversation
Signed-off-by: sotiris tzimas <t8220149@aueb.gr>
alphacrack
approved these changes
Aug 5, 2026
alphacrack
left a comment
alphacrack
left a comment
Owner
There was a problem hiding this comment.
Clean .editorconfig, matches ruff's 120/4-space + 2-space YAML/TOML. CI green. (Tiny follow-up nit: the file is missing its own trailing newline — not blocking.) Thanks! 🎉
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This pull request introduces a root
.editorconfigfile to standardize editor settings across the repository. The configuration ensures consistent indentation, character encoding, line endings, final newline insertion, and whitespace handling, helping contributors produce consistent formatting regardless of their editor or IDE.Motivation
Adding an
.editorconfigfile improves the developer experience by reducing formatting inconsistencies and preventing avoidable formatting-related changes in future pull requests. The configuration is aligned with the project's existing formatting conventions.Closes #48