Merge branch 'develop' into feature/keyboard-shortcuts

Fix CR and conflicts

Author: YairEn

.github/workflows/translatable-string-extract.yml

@@ -0,0 +1,45 @@
+# This workflow will extract new translatable strings from files under /app and /tests into a base.pot file,
+# and update the 'en' and 'he' base.po and base.mo files.
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-python-with-github-actions
+
+name: update-translations
+
+on:
+  # Trigger the workflow on push request,
+  # but only for the main branch
+  push:
+    branches:
+      - main
+
+jobs:
+  update-translations:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+
+      - name: Set up Python 3.x
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+
+      - name: Install prerequesits
+        run: |
+          python -m pip install --upgrade pip
+          pip install Babel Jinja2
+
+      - name: Create base.pot file
+        run: pybabel extract --mapping-file=app/babel_mapping.ini app tests -o app/locales/base.pot -c i18n
+
+      - name: Update all language base.po files
+        run: pybabel update -i app/locales/base.pot -d app/locales -D base
+
+      - name: Update all .mo files
+        run: pybabel compile -d app/locales -D base
+
+      # https://github.com/stefanzweifel/git-auto-commit-action
+      - name: Commit changes
+        uses: stefanzweifel/git-auto-commit-action@v4
+        with:
+          commit_message: Apply automatic translatable string changes

.gitignore

@@ -1,7 +1,6 @@
 dev.db
 test.db
 config.py
-.vscode/settings.json
 
 # Byte-compiled / optimized / DLL files
 __pycache__/
@@ -14,6 +13,8 @@ __pycache__/
 # Distribution / packaging
 .Python
 build/
+Scripts/
+include/
 develop-eggs/
 dist/
 downloads/
@@ -31,6 +32,8 @@ share/python-wheels/
 .installed.cfg
 *.egg
 MANIFEST
+pyvenv.cfg
+
 
 # PyInstaller
 #  Usually these files are written by a python script from a template
@@ -117,8 +120,12 @@ venv/
 ENV/
 env.bak/
 venv.bak/
+.vscode/
 Scripts/*
 pyvenv.cfg
+.history
+calender-venv/
+
 
 # Spyder project settings
 .spyderproject
@@ -138,8 +145,19 @@ dmypy.json
 # Pyre type checker
 .pyre/
 
+# mac env
+bin
+
+# register stuff
+run.txt
+
 # VScode
-.vscode/
+.vscode
 app/.vscode/
 
 app/routers/stam
+
+# PyCharm
+.idea
+
+junit/

.pre-commit-config.yaml

@@ -0,0 +1,37 @@
+repos:
+  # Flake8 to check style is OK
+  - repo: https://gitlab.com/pycqa/flake8
+    rev: 3.8.4
+    hooks:
+    - id: flake8
+  # yapf to fix many style mistakes
+  - repo: https://github.com/ambv/black
+    rev: 20.8b1
+    hooks:
+      - id: black
+        entry: black
+        language: python
+        language_version: python3
+        require_serial: true
+        types_or: [python, pyi]
+  # More built in style checks and fixes
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v3.4.0
+    hooks:
+    - id: trailing-whitespace
+    - id: check-docstring-first
+    - id: check-json
+    - id: check-added-large-files
+    - id: check-yaml
+    - id: debug-statements
+    - id: requirements-txt-fixer
+    - id: check-merge-conflict
+    - id: end-of-file-fixer
+    - id: sort-simple-yaml
+  - repo: meta
+    hooks:
+    - id: check-useless-excludes
+  - repo: https://github.com/asottile/add-trailing-comma
+    rev: v2.1.0
+    hooks:
+    -   id: add-trailing-comma

AUTHORS.md

@@ -0,0 +1,39 @@
+🐍 This document only reflects the team at the time of the original release in February 2021.
+
+# Our Authors
+
+         * Yam Mesicka - Leader
+         * Adva Alkalay - Developer
+         * Aviad Amar - Developer
+         * Efrat Bar Yehuda - Developer
+         * Michael Ben David - Developer
+         * Tamar Berger - Developer
+         * Yuval Cagan - Developer
+         * Elior Digmi - Developer
+         * Adi Faibish - Developer
+         * Yaakov Fogel - Developer
+         * Ori Hirshfeld - Developer
+         * Hadas Kedar - Developer
+         * Hagai Kraus - Developer
+         * Eyal Merav - Developer
+         * Idan Pelled - Developer
+         * Nadav Pesach - Developer
+         * Nir Perelshtein - Developer
+         * Elor Shoshan - Developer
+         * Anna Shtirberg - Developer
+         * Zohar Yamin - Developer
+         * Odelia Yechiel - Developer
+         * Sagi Zaid Or - Developer
+         * Ap1234567 - Developer
+         * ellenc345 - Developer
+         * Gonzom - Developer
+         * ivarshav - Developer
+         * Liad-n - Developer
+         * leddest - Developer
+         * PureDreamer - Developer
+         * ShiZinDle - Developer
+         * YairEn - Developer
+
+# Special thanks to
+
+Yam Mesicka for dedicated accompaniment throughout the year of fascinating Python studies.

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at lms@pythonic.guru. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,25 @@
+# Contributing
+👍🎉 First off, thanks for taking the time to contribute! 🎉👍
+
+When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
+
+Please note we have a [code of conduct](https://github.com/PythonFreeCourse/calendar/blob/master/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Pull Requests
+Create feature branches.
+
+One pull request per feature - If you want to do more than one thing, send multiple pull requests.
+
+Send coherent history - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](https://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.
+
+## Guide
+1. Fork the project.
+2. Create a new branch (`git checkout -b 'branch name'`).
+3. Commit your changes (`git commit -m 'Add something new'`).
+4. Push to the branch (`git push -u origin 'branch name'`).
+5. Open a Pull Request.
+
+## Style Guide
+Follow the [commit messages specification](https://www.conventionalcommits.org/en/v1.0.0/).
+
+Happy coding!

README.md

@@ -1,14 +1,64 @@
 # PyLander
 
-## Open Source Calendar built with Python
+<p style="text-align:center">
+  <img title="Apache-2.0" alt="License Apache-2.0 icon" src="https://img.shields.io/github/license/PythonFreeCourse/calendar.svg">
+</p>
 
-### Run on Windows:
+👋 Welcome to Open Source Calendar built with Python. 🐍
+
+* [Project's objectives](#Project's-objectives)
+* [Creating development environment](#creating-development-environment)
+* [Contributing](#contributing)
+### Project's objectives
+1. Develop open source calendar tool using new technics while trying new things.
+2. Using Python as main programming language and plain HTML/JS for GUI.
+3. Create bonding in our community.
+
+## Creating development environment
+### Prerequisites
+1. Windows or Linux based system - either [WSL on windows](https://docs.microsoft.com/en-us/windows/wsl/install-win10) or full blown linux.
+2. [Python](https://www.python.org/downloads/release/python-385/)
+3. Install python's requirements:
+```shell
+pip install -r requirements.txt
+```
+4. Install pre-commit hooks:
+```shell
+pre-commit install
+```
+
+### Running on Windows
 
 ```shell
 virtualenv env
 .\env\Scripts\activate.bat
 pip install -r requirements.txt
-# Copy configuration.py.example to configuration.py.
+# Copy app\config.py.example to app\config.py.
 # Edit the variables' values.
+# Rendering JWT_KEY:
+python -c "import secrets; from pathlib import Path; f = Path('app/config.py'); f.write_text(f.read_text().replace('JWT_KEY_PLACEHOLDER', secrets.token_hex(32), 1));"
 uvicorn app.main:app --reload
 ```
+
+### Running on Linux
+```shell
+python -m venv venv
+source venv/bin/activate
+pip install -r requirements.txt
+cp app/config.py.example app/config.py
+# Edit the variables' values.
+# Rendering JWT_KEY:
+python -c "import secrets; from pathlib import Path; f = Path('app/config.py'); f.write_text(f.read_text().replace('JWT_KEY_PLACEHOLDER', secrets.token_hex(32), 1));"
+
+### Running tox
+```shell
+# Standard tests: 'coverage' and 'flake8'
+tox
+# Only flake8 tests
+tox -e flake8
+# Coverage with html reports
+tox -e rep
+```
+
+## Contributing
+View [contributing guidelines](https://github.com/PythonFreeCourse/calendar/blob/master/CONTRIBUTING.md).