Add initial configs for coding standards. #58
Conversation
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
Added pre commit config using ruff as a linter and as a formatter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added pre commit config using ruff as linter and formatter.
About this change - What it does
Adds some basic configuration for git hooks using pre-commit framework.
Adds some basic configuration for ruff tool for linting and formatting python code.
Resolves: #25
Why this way
This project is a great testing ground for ruff. As opposed to more stable, battle-tested tools which one may choose for a production project (i.e.: black, flake, pylint, ..).
Ruff formatter is supposedly compatible with black formatter.
Ruff linter can use rules from many commonly used analyzers, parsers, linters.. (i.e.:pyflakes, isort, ..)