Add prettier and fix stylelint upgrade

Author: dmetzner

.dkim/readme.md

@@ -5,4 +5,4 @@ This private key must never be added to the git-history! Ask a product owner in
 
 The corresponding public key must be added to the DNS Dkim entry (Cloudflare).
 
-Note: The private key must be kept valid during deployments.
+Note: The private key must be kept valid during deployments.

.eslintrc.yaml

@@ -10,6 +10,10 @@ globals:
   SharedArrayBuffer: readonly
 parserOptions:
   ecmaVersion: 2018
-rules: {
-  "no-new": 0,
-}
+rules:
+  {
+    'no-new': 0,
+    'comma-dangle': 0,
+    'space-before-function-paren': 0,
+    'indent': 0,
+  }

.github/actions/setup-npm-node-modules/action.yaml

@@ -1,14 +1,14 @@
 name: 'Install node and npm modules'
 description: 'Install node and npm modules. Caching is enabled for enhanced performance.'
 runs:
-  using: "composite"
+  using: 'composite'
   steps:
-    - name: "Download and set up node (caching is enabled)"
+    - name: 'Download and set up node (caching is enabled)'
       uses: actions/setup-node@v3
       with:
         node-version: '20.x'
 
-    - name: "Use caching action to improve performance"
+    - name: 'Use caching action to improve performance'
       id: npm-cache
       uses: actions/cache@v3
       with:
@@ -17,7 +17,7 @@ runs:
         restore-keys: |
           ${{ runner.os }}-node-
 
-    - name: "Only install modules if there is no cache hit"
+    - name: 'Only install modules if there is no cache hit'
       # "If" not yet supported: https://github.com/actions/runner/issues/834 -> shell workaround
       #    - if: steps.npm-cache.outputs.cache-hit != 'true'
       #      run: npm ci
@@ -28,4 +28,4 @@ runs:
           echo "Cache hit - skipping dependency installation"
         else
           npm ci
-        fi
+        fi

.github/actions/setup-php-composer/action.yaml

@@ -1,18 +1,18 @@
 name: 'Install php and composer vendor libraries'
 description: 'Install php and composer vendor libraries. Caching is enabled for enhanced performance.'
 runs:
-  using: "composite"
+  using: 'composite'
   steps:
-    - name: "Setup PHP 8.2"
+    - name: 'Setup PHP 8.2'
       uses: shivammathur/setup-php@v2
       with:
         php-version: 8.2
 
-    - name: "Ensure composer configuration is valid"
+    - name: 'Ensure composer configuration is valid'
       shell: bash
       run: composer validate
 
-    - name: "Use caching action to improve performance"
+    - name: 'Use caching action to improve performance'
       id: composer-cache
       uses: actions/cache@v3
       with:
@@ -29,7 +29,7 @@ runs:
         restore-keys: |
           ${{ runner.os }}-php--
 
-    - name: "Only install packages if there is no cache hit"
+    - name: 'Only install packages if there is no cache hit'
       # "If" not yet supported: https://github.com/actions/runner/issues/834 -> shell workaround
       #      - if: steps.composer-cache.outputs.cache-hit != 'true'
       #        run: composer install --prefer-dist --no-progress
@@ -40,4 +40,4 @@ runs:
           echo "Cache hit - skipping dependency installation"
         else
           composer install --prefer-dist --no-progress
-        fi
+        fi

.github/codecov.yaml

@@ -32,4 +32,4 @@ coverage:
 # it is only QOL change and not required
 #
 comment:
-    after_n_builds: 29
+  after_n_builds: 29

.github/contributing.md

@@ -1,13 +1,15 @@
 # Contributing to Catroweb
+
 :tada: Firstly, thank you for contributing to Catroweb! You are one of the pandas now! :tada:
 
-**PR's** are always appreciated! Please be sure to fill out the 
-[PR Template](https://github.com/Catrobat/Catroweb-Symfony/blob/develop/.github/pull_request_template.md) 
+**PR's** are always appreciated! Please be sure to fill out the
+[PR Template](https://github.com/Catrobat/Catroweb-Symfony/blob/develop/.github/pull_request_template.md)
 as detailed as possible. You will be the hero of everyone who does code reviews. Every pull request will be automatically
 checked against various tests in our GitHub Actions CI system. Make sure all tests are passing!
- When tests are failing the PR will not be accepted.
+When tests are failing the PR will not be accepted.
 
 ### Guides
+
 There are comprehensive Guides and Cheat Sheets available in our [wiki](https://github.com/Catrobat/Catroweb-Symfony/wiki/).
 Make sure to check them out if you have any questions, before asking a project maintainer.
 
@@ -18,30 +20,39 @@ Make sure to check them out if you have any questions, before asking a project m
 3. Implement your logic
 4. Check that all tests pass
 5. Repeat 1-4 if necessary
+
 ##### 6. Create a Pull Request:
 
- Also, make sure that every commit has the **correct commit message layout** so it shows up on [JIRA](https://jira.catrob.at/).<br/>
-  must read: [How to Write a Git Commit Message, by Chirs Beams](http://chris.beams.io/posts/git-commit/)
-  ```
-   Line 1: SHARE-XXX Fitting Title (< 50 chars)
-   Line 2: empty line 
-   Lines 3 - X: actual commit message; first focusing on WHY then focusing on WHAT you have changed.
-  ```
+Also, make sure that every commit has the **correct commit message layout** so it shows up on [JIRA](https://jira.catrob.at/).<br/>
+must read: [How to Write a Git Commit Message, by Chirs Beams](http://chris.beams.io/posts/git-commit/)
+
+```
+ Line 1: SHARE-XXX Fitting Title (< 50 chars)
+ Line 2: empty line
+ Lines 3 - X: actual commit message; first focusing on WHY then focusing on WHAT you have changed.
+```
+
 Squash your commits, there must be only 1 commit! (XX is the number of your commits)
-  ```
-  git reset --soft HEAD~XX &&
-  git commit
-  ```
-  When there is only one commit and you just need to change the commit message you can use:
-  ```
-  git commit --amend
-  ``` 
- Go to GitHub and **create a Pull-Request** from your forked repository into the official repository.<br/>
-   - check that you create the PR from your correct ticket branch!
-   - check that PR goes to the `develop` branch and not `master` branch!
-   - enable "allow edits from maintainers", this allows the Seniors to rebase your PR if needed
+
+```
+git reset --soft HEAD~XX &&
+git commit
+```
+
+When there is only one commit and you just need to change the commit message you can use:
+
+```
+git commit --amend
+```
+
+Go to GitHub and **create a Pull-Request** from your forked repository into the official repository.<br/>
+
+- check that you create the PR from your correct ticket branch!
+- check that PR goes to the `develop` branch and not `master` branch!
+- enable "allow edits from maintainers", this allows the Seniors to rebase your PR if needed
 
 ##### 7. Keep your PR up-to-date and be responsive to requested changes. Make sure the CI tests pass
+
 - **merge-conflicts?** Resolve them and rebase your PR.<br/>
 
   ```
@@ -50,15 +61,16 @@ Squash your commits, there must be only 1 commit! (XX is the number of your comm
   git checkout SHARE-XX
   git rebase -i develop
   ```
+
   Resolve conflicts if necessary (Note: IDE's like Phpstorm have great tools to resolve such conflicts).
+
   ```
   git rebase --continue
   git push -f
   ```
 
-- **requested changes?** 
+- **requested changes?**
 
-  Feel free to discuss them with your code reviewer before blindly accepting them. 
-  Then if necessary apply the changes. 
+  Feel free to discuss them with your code reviewer before blindly accepting them.
+  Then if necessary apply the changes.
   After resolving the changes, don't forget to squash your commits and force push the branch.
- 

.github/dependabot.yaml

@@ -9,43 +9,42 @@
 #
 version: 2
 updates:
+  - package-ecosystem: 'docker'
+    directory: '/docker'
+    schedule:
+      interval: daily
+      time: '04:00'
+      timezone: 'Europe/Vienna'
+    reviewers:
+      - 'dmetzner'
+    open-pull-requests-limit: 99
 
-- package-ecosystem: "docker"
-  directory: "/docker"
-  schedule:
-    interval: daily
-    time: "04:00"
-    timezone: "Europe/Vienna"
-  reviewers:
-    - "dmetzner"
-  open-pull-requests-limit: 99
+  - package-ecosystem: 'npm'
+    directory: '/'
+    schedule:
+      interval: daily
+      time: '04:00'
+      timezone: 'Europe/Vienna'
+    reviewers:
+      - 'dmetzner'
+    open-pull-requests-limit: 99
 
-- package-ecosystem: "npm"
-  directory: "/"
-  schedule:
-    interval: daily
-    time: "04:00"
-    timezone: "Europe/Vienna"
-  reviewers:
-    - "dmetzner"
-  open-pull-requests-limit: 99
+  - package-ecosystem: 'composer'
+    directory: '/'
+    schedule:
+      interval: daily
+      time: '04:00'
+      timezone: 'Europe/Vienna'
+    reviewers:
+      - 'dmetzner'
+    open-pull-requests-limit: 99
 
-- package-ecosystem: "composer"
-  directory: "/"
-  schedule:
-    interval: daily
-    time: "04:00"
-    timezone: "Europe/Vienna"
-  reviewers:
-    - "dmetzner"
-  open-pull-requests-limit: 99
-
-- package-ecosystem: "github-actions"
-  directory: "/"
-  schedule:
-    interval: daily
-    time: "04:00"
-    timezone: "Europe/Vienna"
-  reviewers:
-    - "dmetzner"
-  open-pull-requests-limit: 99
+  - package-ecosystem: 'github-actions'
+    directory: '/'
+    schedule:
+      interval: daily
+      time: '04:00'
+      timezone: 'Europe/Vienna'
+    reviewers:
+      - 'dmetzner'
+    open-pull-requests-limit: 99

.github/onboarding.md

@@ -1,54 +1,58 @@
 This step-by-step guide will support you on your way to your first pull request (PR) at Catrobat. To achieve this, we will guide you through the following steps:
+
 1. Workspace Setup
 2. Finding your first Ticket
 3. Implementing your first ticket using Catrobat's Contribution Workflow
 
 # 1. Workspace Setup
-First, we will show you how to set up your working environment and verify the correctness of this setup.
 
+First, we will show you how to set up your working environment and verify the correctness of this setup.
 
 ## a. Installing the IDE and Tools
-We recommend using [PhpStorm](https://www.jetbrains.com/phpstorm/) as all our contributors do. Please find the IDE version suitable for your operating system on the website and install it on your computer.
 
+We recommend using [PhpStorm](https://www.jetbrains.com/phpstorm/) as all our contributors do. Please find the IDE version suitable for your operating system on the website and install it on your computer.
 
 ## b. Repository Setup
+
 ### (I) Git Setup
+
 At Catrobat, we use Git to keep track of changes in our codebase. If you have not installed Git on your computer yet, please follow the [official guide to set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git).
 
 ### (II) Catrobat's Forking Workflow
+
 To enable the contribution of people like you, we decided to use a forking workflow. In a nutshell, this works as follows. First, everyone who wants to contribute creates (=forks) a personal copy of our repository (=fork). The contributor then makes changes on his fork and informs the community about the changes via a PR. A core contributor will review the changes in the PR. If the changes are accepted, the core contributor will merge the changes into the original repository of Catrobat.
 If you are unfamiliar with Git or have not used it recently, the official guide about [forking a repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) is a good starting point.
 
 ### (III) Setting up your Fork
+
 Now that you know how to work with Git, it is time to set up your fork by executing the following steps. We recommend to use Docker for an easy and seamless setup process:
+
 - [Install Docker](https://github.com/Catrobat/Catroweb/wiki/Docker#install-docker)
 - [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo#forking-a-repository) the [repository of Catroweb](https://github.com/Catrobat/Catroweb)
 - [Clone](https://github.com/Catrobat/Catroweb/wiki/Docker#checkout-the-catroweb-project) the repository
 
 You can find more information about using Catroweb with Docker [here](https://github.com/Catrobat/Catroweb/wiki/Docker#introduction-to-catroweb-with-docker).
 
-
 ## c. Setup Verification
+
 Now you should be able to [run Catroweb in Docker](https://github.com/Catrobat/Catroweb/wiki/Docker#running-catroweb-dev-in-docker) to display the sharing platform similar to our [current version online](https://share.catrob.at/app/).
 
 Note: Make sure that you run the commands through [Git Bash in PhpStorm](https://medium.com/code-complete/using-git-bash-with-phpstorm-10f8d54a96da).
 
-
-
 # 2. Finding your first Ticket
 
-
 ## a. Catrobat's Jira Workflow
+
 At Catrobat, we use Jira to keep track of all issues (stories, tasks, and bugs) in our projects. You can find the Jira project of Catroweb [here](https://jira.catrob.at/projects/SHARE/issues/SHARE-527?filter=allopenissues).
 If you click "Kanban Board" on the left menu in Jira, you will get an overview of what we are currently working on. You can see that different issues have different statuses (e.g., "Ready for Development"). The collection of all statuses makes up our Jira workflow that transparently shows the project's current state to every team member. You can find an overview of our Jira workflow if you click on an issue and the "(View Workflow)" next to the status field.
 It is crucial to follow this workflow to keep the team informed about what you are currently working on.
 
-
 ## b. Choosing a suitable Ticket
-We prepared a [beginner ticket](https://jira.catrob.at/browse/SHARE-532) for our newcomers that should be easy to implement. You will find all the necessary information in the ticket.
 
+We prepared a [beginner ticket](https://jira.catrob.at/browse/SHARE-532) for our newcomers that should be easy to implement. You will find all the necessary information in the ticket.
 
 ## c. Informing the Community
+
 As mentioned earlier, it is essential to keep the team updated. As you do not have the permissions for our Jira project yet, you cannot change the status of the issue you chose. Instead, please assign the ticket to yourself by commenting on it using the following template.
 
 ```diff
@@ -63,10 +67,10 @@ After you have finished your work and submitted a pull request, you have to use
 
 💡 In the upcoming steps, you will find the general workflow of the project. As you do not have permissions for Jira and Confluence yet, please skip all actions that involve Jira ticket status updates and additional information on Confluence!
 
-
-
 # 3. Catrobat's Contribution Workflow
+
 The general workflow of the project involves the following steps:
+
 - Claim a Ticket
 - Do the Work
 - Submit the Changes

.github/pull_request_template.md

@@ -1,23 +1,27 @@
 ---
+
 ### Your checklist for this pull request
+
 Please review the [contributing guidelines](https://github.com/Catrobat/Catroweb-Symfony/blob/develop/.github/contributing.md) and [wiki pages](https://github.com/Catrobat/catroweb-Symfony/wiki/) of this repository.
 
 - [ ] Include the name and id of the Jira ticket in the PR’s title eg.: `SHARE-666 The devils ticket`
-- [ ] Choose the proper base branch (*develop*)
+- [ ] Choose the proper base branch (_develop_)
 - [ ] Confirm that the changes follow the project’s coding guidelines
-- [ ] Verify that the changes generate no warnings and errors 
+- [ ] Verify that the changes generate no warnings and errors
 - [ ] Verify to commit no other files than the intentionally changed ones
 - [ ] Include reasonable and readable tests verifying the added or changed behavior
 - [ ] Verify that all tests are passing (CI), if not please state the test cases in the [section](#Tests) below
 - [ ] Perform a self-review of the changes
 - [ ] Stick to the project’s git workflow (rebase and squash your commits)
 - [ ] Verify that your changes do not have any conflicts with the base branch
 - [ ] Put your ticket into the `Code Review` section in [Jira](https://jira.catrob.at/)
-- [ ] Post a message in the *#catroweb* [Slack channel](https://catrobat.slack.com) and ask for a code reviewer
+- [ ] Post a message in the _#catroweb_ [Slack channel](https://catrobat.slack.com) and ask for a code reviewer
 - [ ] Check that your pull request has been successfully deployed to https://web-test-1.catrob.at/
 
 ### Additional Description
+
 `TODO: Add additional information that is not in your commit-message here`
 
 ### Tests - additional information
+
 `TODO: add additional information about testruns here`