chore: integrate pre-commit (#1117)

* integrate pre-commit
* run isort with profile black
* run Trim Trailing Whitespace
* run end-of-file-fixer
* fix flake8 F401: import not used error
* fix flake8 F841: local variable assigned to but never used error
* fix flake8 F541: f-string is missing placeholders error
* make isort black compatible
* run black compatible isort
* fix E712: comparison to True should be 'if cond:' error
* fix E266: too many leading '#' error
* fix F403: 'import *' used error
* fix E402: module level import not at top of file error
* remove ignored errors from .flake8
* document pre-commit and isort
* ignore W503, E501 & C901
* Update README.md
* Update README.md
* don't remove migrate

Author: KushalBeniwal

.coveragerc

@@ -1,4 +1,4 @@
 [run]
-omit = 
+omit =
     # omit everything in the tests directory
     tests/*

.flake8

@@ -0,0 +1,13 @@
+[flake8]
+ignore =
+    # W503: line break before binary operator
+    # ignored as it creates inconsistency with black
+    W503,
+    # E501: line too long (> 88 characters)
+    # ignored till a final decision is made on what to do with long comments
+    E501,
+    # C901: variable or function name is too complex (> 18 characters)
+    # ignored till someone simplifies the names
+    C901
+max-line-length = 88
+max-complexity = 18

.github/CONTRIBUTING.md

@@ -7,16 +7,16 @@
 * When developing a new feature, include at least one test when applicable.
 * When submitting a PR, please follow [this template](PULL_REQUEST_TEMPLATE.md) (which will probably be already filled up once you create the PR).
 * When submitting a PR with changes to user interface (e.g.: new screen, or an email template), please add screenshots to the PR description.
-* When you are finished with your work, please squash your commits otherwise we will squash them on your PR (this can help us maintain a clear commit history). 
+* When you are finished with your work, please squash your commits otherwise we will squash them on your PR (this can help us maintain a clear commit history).
 * When writing in-code documentation as Docstrings, please follow [this guide](https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings).
 * When creating an issue to report a bug in the project, please follow our [bug_report.md](https://github.com/anitab-org/.github/blob/main/.github/ISSUE_TEMPLATE/bug_report.md) template.
 
 ## General Guidelines
 
 * If you’re just getting started work on an issue labeled “First Timers Only” in any project. Additional resources are available on our [website](http://www.systers.io).
-* In an active repository (not an archived one), choose an open issue from the issue list, claim it in the comments, and a maintainer will assign it to you.  
+* In an active repository (not an archived one), choose an open issue from the issue list, claim it in the comments, and a maintainer will assign it to you.
 * After approval you must make continuous notes on your progress in the issue while working.  If there is not at least one comment every 3 days, the maintainer can reassign the issue.
 * Create a branch specific to the issue you're working on, so that you send a PR from that branch instead of the base branch on your fork.
-* If you’d like to create a new issue, please go through our issue list first (open as well as closed) and make sure the issues you are reporting do not replicate the existing issues. 
+* If you’d like to create a new issue, please go through our issue list first (open as well as closed) and make sure the issues you are reporting do not replicate the existing issues.
 * Have a short description on what has gone wrong (like a root cause analysis and description of the fix), if that information is not already present in the issue.
 * If you have issues on multiple pages, report them separately. Do not combine them into a single issue.

.github/PULL_REQUEST_TEMPLATE.md

@@ -41,7 +41,7 @@ Fixes # [ISSUE]
 
 **Code/Quality Assurance Only**
 
-- [ ] My changes generate no new warnings 
+- [ ] My changes generate no new warnings
 - [ ] My PR currently breaks something (fix or feature that would cause existing functionality to not work as expected)
 - [ ] I have added tests that prove my fix is effective or that my feature works
 - [ ] New and existing unit tests pass locally with my changes

.github/config.yml

@@ -7,7 +7,7 @@ newIssueWelcomeComment: |
   Hello there!👋 Welcome to the project!💖
 
   Thank you and congrats 🎉 for opening your very first issue in this project.
-  AnitaB.org Open Source is an inclusive community, committed to creating a safe and positive environment 🌸  Please follow our [Code Of Conduct](https://github.com/anitab-org/mentorship-backend/blob/develop/docs/code_of_conduct.md) 🙌 
+  AnitaB.org Open Source is an inclusive community, committed to creating a safe and positive environment 🌸  Please follow our [Code Of Conduct](https://github.com/anitab-org/mentorship-backend/blob/develop/docs/code_of_conduct.md) 🙌
   You can learn more about the community on [our website](https://anitab-org.github.io/) and [documentation repository](https://github.com/anitab-org/documentation#readme).
 
   You may submit a PR on the same if you like!
@@ -39,7 +39,7 @@ firstPRMergeComment: |
   Woohoo!🎊 Congrats on merging your first contribution to [mentorship-backend](https://github.com/anitab-org/mentorship-backend)!✨
   Your code is officially a part of AnitaB.org Open Source now!! Time for a celebration 🙌🎉⚡️
   Feel free to explore more on this project.🤗
-  Join us on [AnitaB.org Open Source Zulip](https://anitab-org.zulipchat.com/). 🤝 
+  Join us on [AnitaB.org Open Source Zulip](https://anitab-org.zulipchat.com/). 🤝
   We have different streams for each active repository for discussions. 👩🏽‍💻🧑🏼‍💻
   Do join our weekly check-in stream to share your weekly goals and the awesome work you did here.😃
 

.github/workflows/main.yml

@@ -6,12 +6,12 @@ name: Lint Code and Run Tests
 on:
   pull_request:
     branches: [develop]
-    paths-ignore: 
+    paths-ignore:
       - '**.md'
       - /docs/CODEOWNERS
   push:
     branches: [develop]
-    paths-ignore: 
+    paths-ignore:
       - '**.md'
       - /docs/CODEOWNERS
 
@@ -21,7 +21,7 @@ jobs:
     steps:
       - uses: actions/checkout@v2
       - uses: actions/setup-python@v2
-      - uses: psf/black@stable      
+      - uses: psf/black@stable
 
   build:
     needs: lint

.isort.cfg

@@ -0,0 +1,9 @@
+[tool.isort]
+profile = "black"
+multi_line_output = 3
+
+[settings]
+line_length = 88
+multi_line_output = 3
+include_trailing_comma = True
+known_third_party = celery,django,environ,pyquery,pytz,redis,requests,rest_framework

.pre-commit-config.yaml

@@ -0,0 +1,21 @@
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v2.3.0
+    hooks:
+    -   id: check-yaml
+    -   id: end-of-file-fixer
+    -   id: trailing-whitespace
+-   repo: https://github.com/psf/black
+    rev: 21.5b1
+    hooks:
+    -   id: black
+        args: [--check]
+-   repo: https://gitlab.com/pycqa/flake8
+    rev: 3.9.2
+    hooks:
+    - id: flake8
+-   repo: https://github.com/pycqa/isort
+    rev: 5.8.0
+    hooks:
+      - id: isort
+        args: [--profile, black, -c]

README.md

@@ -209,6 +209,35 @@ To run black:
 black .
 ```
 
+#### Sorting imports with isort
+
+We use [_isort_](https://pypi.org/project/isort/) to sort imports alphabetically, and automatically separated into
+sections and by type. To install _isort_:
+
+```
+pip install isort
+```
+
+To run isort:
+
+```
+isort . --profile=black
+```
+
+#### Automate auto-formatting tools with pre-commit
+
+We use [_pre-commit_](https://pre-commit.com/) to check formatting before every commit message. To install _pre-commit_:
+
+```
+pip install pre-commit
+```
+
+To set up the git hook scripts:
+
+```
+pre-commit install
+```
+
 ## Documentation
 
 Documentation for the project is hosted [here](https://anitab-org.github.io/mentorship-backend/). We use Docusaurus for maintaining the documentation of the project.

app/api/api_extension.py

@@ -1,14 +1,15 @@
 from flask_restx import Api
 
-# Adding namespaces
-from app.api.resources.user import users_ns as user_namespace
 from app.api.resources.admin import admin_ns as admin_namespace
 from app.api.resources.mentorship_relation import (
     mentorship_relation_ns as mentorship_namespace,
 )
 from app.api.resources.task import task_ns as task_namespace
 from app.api.resources.task_comment import task_comment_ns as task_comment_namespace
 
+# Adding namespaces
+from app.api.resources.user import users_ns as user_namespace
+
 
 def androidlink():
     return "<a href=https://github.com/anitab-org/mentorship-android>Android</a>"