add linter, editorconfig and pre-commit hooks #22
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 pull request introduces a standardized linting and formatting setup for the project. It adds configuration files for editor and linting tool consistency, and provides a custom Python script to run all linting checks in a unified way. These changes will help ensure code style consistency and catch common errors before code review.
Linting and Formatting Tooling:
.editorconfig
to enforce consistent indentation, line endings, and whitespace rules across editors and file types..pre-commit-config.yaml
to configure pre-commit hooks for tools like Black, isort, Ruff, and MyPy, automating code formatting, linting, and type checking.Developer Workflow Improvements:
lint.py
script that runs all configured linting and formatting tools (Black, isort, Ruff, and MyPy) with clear output, making it easy for developers to check code quality locally.