-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Code Quality with Automated Formatting and Linting #32
Comments
This suggestion might be redundant if Black is already applied since Black is a highly opinionated formatter that overrides other tools' formatting rules. What do you think @ramazanoacar ? |
Hello @berkingurcan Actually, I find it very useful to use isort or any other approach (maybe manually) for sorting and dividing the imports according to their types. Maybe, this issue and that one could be summed up to a bigger issue of fully refactoring the repo with addition of the following subtasks:
|
Thank you for suggestions, yes it is a good idea to concatenate these issues. @CyrilBaah What do you think? |
Enhance code formatting and Linting Standards with Pre-configured Tools (Black, Flake8, Isort)
Ensure code adheres to formatting standards and best practices, catching issues early in the CI/CD pipeline.
Automating these tools will streamline code reviews, improve quality, and simplify adherence to Python best practices for all contributors.
The text was updated successfully, but these errors were encountered: