chore: fix file-formatter hooks exclude regex

.env-template

@@ -14,4 +14,4 @@ MONGODB_DATABASE=test
 MONGODB_USERNAME=root
 MONGODB_PASSWORD=mongodb
 MONGODB_HOSTNAME=db
-MONGODB_PORT=27017
+MONGODB_PORT=27017

.gitattributes

@@ -10,4 +10,4 @@
 
 # Ignore massive diffs each time you add/update yarn plugins
 /web/.yarn/releases/** binary
-/web/.yarn/plugins/** binary
+/web/.yarn/plugins/** binary

.github/ISSUE_TEMPLATE/bug-report.md

@@ -10,4 +10,4 @@ assignees: ''
 
 #### Actual Behaviour
 
-#### Steps to Reproduce
+#### Steps to Reproduce

.github/ISSUE_TEMPLATE/code-maintenance.md

@@ -11,4 +11,4 @@ assignees: ''
 
 #### Suggest Changes
 
-#### Provide Examples
+#### Provide Examples

.github/ISSUE_TEMPLATE/feature-request.md

@@ -10,4 +10,4 @@ assignees: ''
 
 #### Suggest Solution
 
-#### Additional Details
+#### Additional Details

.github/labels.yml

@@ -102,4 +102,4 @@
 - # perf
   name: "type: :speedboat: perf"
   description: ""
-  color: "FBCA04"
+  color: "FBCA04"

.github/pull_request_template.md

@@ -6,4 +6,4 @@ This pull request is needed because of....
 
 Write summary of what this pull request changes if needed.
 
-## Issues related to this change:
+## Issues related to this change:

.gitignore

@@ -165,4 +165,4 @@ web/.yarn/*
 !web/.yarn/**/lib/
 
 # Asdf package manager
-/*/.tool-versions
+/*/.tool-versions

.pre-commit-config.yaml

@@ -20,11 +20,11 @@ repos:
       - id: check-toml
       - id: check-yaml
       - id: trailing-whitespace
-        exclude: ^.*\.(lock)$||^docs\/
+        exclude: ^.*\.(lock)$
       - id: end-of-file-fixer
-        exclude: ^.*\.(lock)$||^docs\/
+        exclude: ^.*\.(lock)$
       - id: mixed-line-ending
-        exclude: ^.*\.(lock)$||^docs\/
+        exclude: ^.*\.(lock)$
       - id: detect-private-key
         exclude: api/src/authentication/mock_token_generator.py
       - id: no-commit-to-branch

README.md

@@ -21,13 +21,13 @@ This is a **solution template** for creating a Single Page App (SPA) with React
 [Development](#development) •
 [Contributing](#contributing)
 
-<!--- The demo project is not currently deployed. 
+<!--- The demo project is not currently deployed.
 A demo is running at https://template-fastapi-react.app.playground.radix.equinor.com
 -->
 
 </div>
 
- 
+
 <a id="key-features"></a>
 ## :dart: Key features
 
@@ -84,4 +84,4 @@ Thanks for your interest in contributing! There are many ways to contribute to t
 [license]: https://github.com/equinor/boilerplate-clean-architecture/blob/main/LICENSE
 [releases]: https://github.com/equinor/boilerplate-clean-architecture/releases
 [on-push-main-branch-badge]: https://github.com/equinor/boilerplate-clean-architecture/actions/workflows/on-push-main-branch.yaml/badge.svg
-[on-push-main-branch-action]: https://github.com/equinor/boilerplate-clean-architecture/actions/workflows/on-push-main-branch.yaml
+[on-push-main-branch-action]: https://github.com/equinor/boilerplate-clean-architecture/actions/workflows/on-push-main-branch.yaml

docker-compose.ci.yml

@@ -24,5 +24,3 @@ services:
       MONGO_INITDB_ROOT_USERNAME: root
       MONGO_INITDB_ROOT_PASSWORD: mongodb
       MONGO_INITDB_DATABASE: db
-
-

documentation/diagrams/fast-api.drawio

@@ -1 +1 @@
-<mxfile host="0gaqkmiououjhbe91jdr6mkdkvq34u9muqfkfht5jjjse7j1klhj" modified="2022-12-20T10:40:45.765Z" agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 13_0_0) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.73.1 Chrome/102.0.5005.167 Electron/19.0.17 Safari/537.36" etag="zfOuhXqEor3Hr5GjEtM-" version="12.2.4" pages="1"><diagram id="lvN6wUeanX1LqGzwJO_P" name="Page-1">3Vpbk9smFP41nkkfsiMEuj1mb0ln2hlPN502j1QiMo0sXITXdn99wYK1JVjXyUpGuy+2OICA73zncA5iBm+W248crxa/soJUszAotjN4OwtDECWJ/FOSXSvJgrgVlJwWutFB8ED/JVoYaOmaFqTpNBSMVYKuusKc1TXJRUeGOWebbrOvrOqOusIlsQQPOa5s6R+0EItWmobJQf6J0HJhRgZx1tYssWmsV9IscME2RyJ4N4M3nDHRPi23N6RS4Blc2n73z9Q+TYyTWpzTQc/rEVdrvTY9L7Ezi+VsXRdEtQ9m8HqzoII8rHCuajdSvVK2EMtKloB8tMfXU3okXJDtkUjP5yNhSyL4TjbRtWGgsdHkiDJd3hyghka2OIY50kKs1Vs+vfuAgHzQILgBQdMDBERpBxCIIgsQFEcOQEzDlwASW+snhTQGXWRcLFjJalzdHaTXXYQObX5hbKVx+ZsIsdOWjdeCnYlaw9Y81/PQmhGYl0S3gq1IzfAkspxUWNDHrjm/BKXQos2nz5/nUvIb+WdNGnGCROAiJIKwa1Uhsq0KhA6rigcwqgj5IBHZUvGn6n4V6dKXo5rbrX7zvrAzhVou7aiTKn45rjt025dMv7MIC23Cpr4ICy3C/v5Ic8ZrRQnGvxE+OcrC9EzKpkNQ9gQ+73Czq/O9VvbG3ajxcV1UhP9koSYXK7rQNIKzb+SGVYxLSc1qxfavtKp6IlzRspbFXEIo1QGvFXRURiEfdMWSFsXeVFy66JrPENuQCWKMOiKHOlKHOsIB1AHTyW5DqW3VZtO8vFkj8JpwgpkvnFLLvB/kxCq5SqKGY2tB6/Lt2jKE2VXUsebIZc0BGMeaAbDgv8eN+DD/WQrbX1IXK0Zr5VvjSoH+l9yQ4lI9vZNpnYS9ku62ecP+FgLU0VAcODQUj+RvgRd/O2r0BRz5AvDmqM1sppsxgMxjxgCyye5jwBHGg8gbj+xAfmI8QonPzBN68WMvyzyTEZxfZJPWW+4JTiVXE0k++6y9bPIZ+WVt8kO0DUegbTwl2sbTp21/074obc17p7sX9b8tIOjKekaKqUM765kYPBAhj/BMPiJGqUf2oNcYyQy/I4SOHQGFvraE0N4SZolcSFBggeXfLLn1zton9plzhPBM1qIhWOvnHOFlrE0hPObt++AqQMn/kHdfmhNOJUTq8Og7GJ3ZjDaOxQOjXTcC7gUrWKPekVzLhhMgNUp6h2OuOGc0Uns5nHg2QQQ/6lfH9aG661yd4h55o6x77pz0A8/WNHSvnk6epnFeFuXlW8izCdEgajLmObaaUNb92Jck6VhqgnbWMN8VuBY0P+FmLnT1pg+Dw8047yINcRUJ2vnCbRtWSAmVEQZltYXQ2/n8gXrQX/IDFfJ8ADORYBs6QpPhPdDZ9uAITaYWbPePDS8bbCevkLUgDfvBdjBesG3CnGkE22Y2zmB7amnjiBG2LB6uPLchxOHiOLz7Dw==</diagram></mxfile>
+<mxfile host="0gaqkmiououjhbe91jdr6mkdkvq34u9muqfkfht5jjjse7j1klhj" modified="2022-12-20T10:40:45.765Z" agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 13_0_0) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.73.1 Chrome/102.0.5005.167 Electron/19.0.17 Safari/537.36" etag="zfOuhXqEor3Hr5GjEtM-" version="12.2.4" pages="1"><diagram id="lvN6wUeanX1LqGzwJO_P" name="Page-1">3Vpbk9smFP41nkkfsiMEuj1mb0ln2hlPN502j1QiMo0sXITXdn99wYK1JVjXyUpGuy+2OICA73zncA5iBm+W248crxa/soJUszAotjN4OwtDECWJ/FOSXSvJgrgVlJwWutFB8ED/JVoYaOmaFqTpNBSMVYKuusKc1TXJRUeGOWebbrOvrOqOusIlsQQPOa5s6R+0EItWmobJQf6J0HJhRgZx1tYssWmsV9IscME2RyJ4N4M3nDHRPi23N6RS4Blc2n73z9Q+TYyTWpzTQc/rEVdrvTY9L7Ezi+VsXRdEtQ9m8HqzoII8rHCuajdSvVK2EMtKloB8tMfXU3okXJDtkUjP5yNhSyL4TjbRtWGgsdHkiDJd3hyghka2OIY50kKs1Vs+vfuAgHzQILgBQdMDBERpBxCIIgsQFEcOQEzDlwASW+snhTQGXWRcLFjJalzdHaTXXYQObX5hbKVx+ZsIsdOWjdeCnYlaw9Y81/PQmhGYl0S3gq1IzfAkspxUWNDHrjm/BKXQos2nz5/nUvIb+WdNGnGCROAiJIKwa1Uhsq0KhA6rigcwqgj5IBHZUvGn6n4V6dKXo5rbrX7zvrAzhVou7aiTKn45rjt025dMv7MIC23Cpr4ICy3C/v5Ic8ZrRQnGvxE+OcrC9EzKpkNQ9gQ+73Czq/O9VvbG3ajxcV1UhP9koSYXK7rQNIKzb+SGVYxLSc1qxfavtKp6IlzRspbFXEIo1QGvFXRURiEfdMWSFsXeVFy66JrPENuQCWKMOiKHOlKHOsIB1AHTyW5DqW3VZtO8vFkj8JpwgpkvnFLLvB/kxCq5SqKGY2tB6/Lt2jKE2VXUsebIZc0BGMeaAbDgv8eN+DD/WQrbX1IXK0Zr5VvjSoH+l9yQ4lI9vZNpnYS9ku62ecP+FgLU0VAcODQUj+RvgRd/O2r0BRz5AvDmqM1sppsxgMxjxgCyye5jwBHGg8gbj+xAfmI8QonPzBN68WMvyzyTEZxfZJPWW+4JTiVXE0k++6y9bPIZ+WVt8kO0DUegbTwl2sbTp21/074obc17p7sX9b8tIOjKekaKqUM765kYPBAhj/BMPiJGqUf2oNcYyQy/I4SOHQGFvraE0N4SZolcSFBggeXfLLn1zton9plzhPBM1qIhWOvnHOFlrE0hPObt++AqQMn/kHdfmhNOJUTq8Og7GJ3ZjDaOxQOjXTcC7gUrWKPekVzLhhMgNUp6h2OuOGc0Uns5nHg2QQQ/6lfH9aG661yd4h55o6x77pz0A8/WNHSvnk6epnFeFuXlW8izCdEgajLmObaaUNb92Jck6VhqgnbWMN8VuBY0P+FmLnT1pg+Dw8047yINcRUJ2vnCbRtWSAmVEQZltYXQ2/n8gXrQX/IDFfJ8ADORYBs6QpPhPdDZ9uAITaYWbPePDS8bbCevkLUgDfvBdjBesG3CnGkE22Y2zmB7amnjiBG2LB6uPLchxOHiOLz7Dw==</diagram></mxfile>

documentation/docs/about/01-introduction.md

@@ -4,4 +4,4 @@
 
 This is a solution template for creating a Single Page App (SPA) with React and FastAPI following the principles of Clean Architecture.
 
-The template provides an example implementation of a todo application. The todo app implementation is fairly basic. A user can add a task, mark a task as completed and delete an added task. The purpose of the minimalist todo app implementation is to learn and practice what the concepts of [clean architecture](../contribute/development-guide/coding/01-architecture.md) are, and how they can be used in a REST API. 
+The template provides an example implementation of a todo application. The todo app implementation is fairly basic. A user can add a task, mark a task as completed and delete an added task. The purpose of the minimalist todo app implementation is to learn and practice what the concepts of [clean architecture](../contribute/development-guide/coding/01-architecture.md) are, and how they can be used in a REST API.

documentation/docs/about/02-overview.md

@@ -2,25 +2,25 @@
 
 ## Getting started
 
-In order to start using this template for your own project, go to [equinor/template-fastapi-react](https://github.com/equinor/template-fastapi-react) and click the `Use this template` button to create a copy. 
+In order to start using this template for your own project, go to [equinor/template-fastapi-react](https://github.com/equinor/template-fastapi-react) and click the `Use this template` button to create a copy.
 
-Next, go-to the instructions on how-to [run locally](running/01-prerequisites.md) . 
+Next, go-to the instructions on how-to [run locally](running/01-prerequisites.md) .
 
 For setting up a development environment, go to the [development guide](../contribute/development-guide/01-setup.md). Next, to start coding and extending the template see the [coding section](../contribute/development-guide/coding/01-architecture.md).
 
 For starting contributing to the template see [contribute section](../contribute/01-how-to-start-contributing.md).
- 
+
 ## Project structure
 
-Here’s how the app is organized. 
+Here’s how the app is organized.
 
 ```
 ├── api/ - backend code
 │── web/ - frontend code
 │── documentation/ - documentation
-├── nginx/ - reverse proxy 
+├── nginx/ - reverse proxy
 ├── .env-template - template for environment variables
 ├── docker-compose.override.yml - for running locally
 ├── docker-compose.yml - common docker compose settings
 └── ...
-```
+```

documentation/docs/about/concepts/01-task.md

@@ -2,11 +2,11 @@
 
 :::info
 
-This is an example of a "concept" which is domain specific, and not related to your application. It should be replaced by relevant domain specific concepts in your documentation. Note that for some concepts, having an "Examples"-section does not make sense. Feel free to adapt the example's structure to best suit your concepts. 
+This is an example of a "concept" which is domain specific, and not related to your application. It should be replaced by relevant domain specific concepts in your documentation. Note that for some concepts, having an "Examples"-section does not make sense. Feel free to adapt the example's structure to best suit your concepts.
 
-::: 
+:::
 
-A task is piece of work which is assigned to be done by one or multiple persons. A task usually has defined limits, often referred to as the task description. 
+A task is piece of work which is assigned to be done by one or multiple persons. A task usually has defined limits, often referred to as the task description.
 
 In order to remember assigned tasks, they are often made note of in lists. Traditionally, these lists have been written on small notes (e.g. post-its), but in recent years there have been a large number of todo-apps developed for phones and computers, replacing its analogue predecessor. See [related concepts](#related-concepts) for more on to-do lists.
 
@@ -15,12 +15,9 @@ Once a task is assigned to a person, the person is expected to carry out the tas
 ## Examples
 
 1. Many young children are given chores around the house, such as taking out the trash or cleaning their room.
-2. All employees have a set of tasks to complete, which are often defined in their contract or verbally during their training. 
+2. All employees have a set of tasks to complete, which are often defined in their contract or verbally during their training.
 
 ## Related concepts
 
 - [To-do list](01-task.md) <!-- Actually link to the other concept here. -->
 - xxx
-
-
-

documentation/docs/about/concepts/02-use-case.md

@@ -11,6 +11,3 @@ For a meetup.com clone, it could be:
 * Drafting new meeting as an organizer
 
 ## Related concepts
-
-
-

documentation/docs/about/concepts/_category_.json

@@ -5,4 +5,4 @@
     "type": "generated-index",
     "description": "General introductions to complex domain-specific topics."
   }
-}
+}

documentation/docs/about/how-to/01-how-to-do-something.md

@@ -1,5 +1 @@
 # How to do something
-
-
-
-

documentation/docs/about/running/01-prerequisites.md

@@ -5,4 +5,4 @@ In order to run you need to have installed:
 - [Docker](https://www.docker.com/)
 - [Docker Compose](https://docs.docker.com/compose/)
 - Git
-- [Python](https://www.python.org/) (3.10 or newer)
+- [Python](https://www.python.org/) (3.10 or newer)

documentation/docs/about/running/02-configure.md

@@ -4,7 +4,7 @@ This document goes through all the different configuration options available.
 
 :::info
 
-Remember to restart 
+Remember to restart
 
 Any changes you make to this file will only come into effect when you restart the
 server.
@@ -24,7 +24,7 @@ First, let's look at the options available in the `.env` file.
 - `TENANT_ID`: Find tenant ID through the Azure portal under Azure Active Directory service. Select properties and under scroll down to the Tenant ID field.
 - `AUTH_SCOPE`: Find the scope the Azure portal under Azure Active Directory service and App registrations. The scope is located under the expose an API.
 
-### API 
+### API
 
 #### System
 
@@ -50,4 +50,4 @@ First, let's look at the options available in the `.env` file.
 Used by the docs:
 
 - `OAUTH_CLIENT_ID`: Find the app's client ID under Azure Active Directory service (also called application ID). The client ID is used to tell Azure which resource a user is attempting to access.
-- `OAUTH_AUTH_SCOPE`: Find the scope the Azure portal under Azure Active Directory service and App registrations. The scope is located under the expose an API.
+- `OAUTH_AUTH_SCOPE`: Find the scope the Azure portal under Azure Active Directory service and App registrations. The scope is located under the expose an API.

documentation/docs/about/running/03-starting-services.md

@@ -29,4 +29,4 @@ Navigate to the /web folder, and then start web application:
 yarn start
 ```
 
-</details>
+</details>

documentation/docs/changelog/changelog.md

@@ -12,4 +12,4 @@ import Contributing, {toc as ChangelogTOC} from "@site/../CHANGELOG.md"
 <Contributing />
 
 export const toc = ChangelogTOC;
-```
+```

documentation/docs/contribute/01-how-to-start-contributing.md

@@ -16,31 +16,31 @@ You can start by looking through the [good first issues](https://github.com/equi
 
 ## Fork the repository
 
-In general, we follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr). 
+In general, we follow the ["fork-and-pull" Git workflow](https://github.com/susam/gitpr).
 
 Here's a quick guide:
 
-1. Create your own fork of the repository 
+1. Create your own fork of the repository
 2. Clone the project to your machine
 3. To keep track of the original repository add another remote named upstream
 ```shell
 git remote add upstream [email protected]:equinor/template-fastapi-react.git
 ```
-4. Create a branch locally with a succinct but descriptive name and prefixed with change type. 
+4. Create a branch locally with a succinct but descriptive name and prefixed with change type.
 ```shell
 git checkout -b feature/my-new-feature
 ```
-5. Make the changes in the created branch. 
+5. Make the changes in the created branch.
 6. Add and run tests for your changes (we only take pull requests with passing tests).
 ```shell
 docker-compose run --rm api pytest
 docker-compose run --rm web yarn test
 ```
-7. Add the changed files 
+7. Add the changed files
 ```shell
 git add path/to/filename
 ```
-8. Commit your changes using the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) formatting for the commit messages. 
+8. Commit your changes using the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) formatting for the commit messages.
 ```shell
 git commit -m "conventional commit formatted message"
 ```
@@ -53,12 +53,12 @@ git rebase upstream/main
 ```shell
 git push origin feature/my-new-feature
 ```
-11. Submit a pull request to the original repository (via Github interface). Please provide us with some explanation of why you made the changes you made. For new features make sure to explain a standard use case to us. 
+11. Submit a pull request to the original repository (via Github interface). Please provide us with some explanation of why you made the changes you made. For new features make sure to explain a standard use case to us.
 
 That's it... thank you for your contribution!
 
-After your pull request is merged, you can safely delete your branch. 
+After your pull request is merged, you can safely delete your branch.
 
 ## Code review process
 
-The core team looks at pull requests on a regular basis. After feedback has been given we expect responses within three weeks. After three weeks we may close the pull request if it isn't showing any activity.
+The core team looks at pull requests on a regular basis. After feedback has been given we expect responses within three weeks. After three weeks we may close the pull request if it isn't showing any activity.

documentation/docs/contribute/02-ground-rules.md

@@ -1,29 +1,29 @@
 # Ground rules
 
-* For major changes, please open an issue first to discuss what you would like to change. 
+* For major changes, please open an issue first to discuss what you would like to change.
   * Search for existing issues and pull requests on the [project development board](https://github.com/equinor/template-fastapi-react/projects/1) before creating your own.
 * Contributors should fork the repository and work on fixes or enhancements on their own fork.
   * Use the [pull request feature](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) to submit your changes to this  repository.
   * All pull requests should be rebased (with main) and commits squashed prior to the final merge process.
   * Use [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) formatting for commit messages, so that it's possible to auto-generate the changelogs.
-* Use a separate branch for each issue you’re working on. 
-  * Do not combine fixes for multiple issues into one branch. 
+* Use a separate branch for each issue you’re working on.
+  * Do not combine fixes for multiple issues into one branch.
 * Please include unit tests with all your code changes.
   * All unit tests must be 100% passing before the pull requests will be approved and merged.
-  
+
 ## Pull Requests
 
 Please try to make your pull request easy to review for us.
 
 * Make small pull requests. The smaller, the faster to review and the more likely it will be merged soon.
-* Don't make changes unrelated to the goals of your PR. 
+* Don't make changes unrelated to the goals of your PR.
   * There might be typos on some comments, or perhaps a function is in need of refactoring - regardless, if those changes are not related to your PR, please implement those changes in another PR.
 
 While you're writing up the pull request, you can add Closes #XXX in the message body where #XXX is the issue you're fixing. Therefore, an example would be Closes #42 would close issue #42.
 
 ## Git commit format
 
-We have very precise rules over how our git commit messages can be formatted. 
+We have very precise rules over how our git commit messages can be formatted.
 
 We are using the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) formatting for commit messages.
 
@@ -45,10 +45,10 @@ The type can be one of these types: feat, fix, build, ci, docs, style, refactor,
 
 Summary should:
 
-* Be written in imperative, present tense, e.g. write `add` instead of `added` or `adds`. 
-* Don't capitalize the first letter. 
+* Be written in imperative, present tense, e.g. write `add` instead of `added` or `adds`.
+* Don't capitalize the first letter.
 * Don't write dot (.) at the end.
- 
+
 :::
 
 <details>
@@ -73,7 +73,7 @@ git commit -a -m "feat(new-parser): introduces a new parsing library
 BREAKING CHANGE: new library does not support foo-construct"
 ```
 
-Complete: 
+Complete:
 
 ```
 refactor!: foo-bar replaces bar-foo