chore: run prettier on all MD and yaml files

.github/ISSUE_TEMPLATE/bug_template.yml

@@ -59,7 +59,7 @@ body:
     attributes:
       label: "📋 Logs"
       description: "Share any relevant log output or error messages."
-  
+
   - type: dropdown
     id: browsers
     attributes:
@@ -79,7 +79,7 @@ body:
       label: "💻 Operating System"
       description: "Which operating system(s) is affected?"
       multiple: true
-      options: 
+      options:
         - Windows
         - Linux
         - macOS

.github/pull_request_template.md

@@ -4,25 +4,32 @@
 
 ## 🚀 Pull Request Checklist
 
-- **Title:** 
+- **Title:**
+
   - `[ ]` A brief, descriptive title for the changes.
 
 - **Description:**
+
   - `[ ]` Provide a clear and concise description of your pull request, including the purpose of the changes and the approach you've taken.
 
 - **Context:**
+
   - `[ ]` Why are these changes necessary? What problem do they solve? Link any related issues.
 
 - **Changes:**
+
   - `[ ]` List the major changes you've made, ideally organized by commit or feature.
 
 - **Testing:**
+
   - `[ ]` Describe how the changes have been tested. Include any relevant details about the testing environment and the test cases.
 
 - **Screenshots (if applicable):**
+
   - `[ ]` If your changes are visual, include screenshots to help explain your changes.
 
 - **Additional Information:**
+
   - `[ ]` Add any other information that might be useful for reviewers, such as considerations, discussions, or dependencies.
 
 - **Checklist:**
@@ -31,4 +38,4 @@
   - `[ ]` I have made corresponding changes to the documentation (if applicable).
   - `[ ]` My changes generate no new warnings or errors.
   - `[ ]` 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.
+  - `[ ]` New and existing unit tests pass locally with my changes.

.github/workflows/release.yml

@@ -12,7 +12,7 @@ on:
 env:
   REGISTRY: ghcr.io
   IMAGE_NAME: ghcr.io/genomicdatainfrastructure/gdi-userportal-dataset-discovery-service
- 
+
 jobs:
   ort:
     strategy:
@@ -43,7 +43,7 @@ jobs:
       - name: Set up GraalVM JDK 21
         uses: graalvm/setup-graalvm@v1
         with:
-          java-version: '21'
+          java-version: "21"
 
       - name: Checkout repository
         uses: actions/checkout@v4
@@ -97,4 +97,3 @@ jobs:
           push: true
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
-

.github/workflows/test.yml

@@ -16,7 +16,7 @@ jobs:
       - name: Set up GraalVM JDK 21
         uses: graalvm/setup-graalvm@v1
         with:
-          java-version: '21'
+          java-version: "21"
       - name: run tests
         run: mvn --batch-mode --update-snapshots verify formatter:validate
       - name: run sonar

CHANGELOG.md

@@ -41,9 +41,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - feat: #26 add facet query operator by @sulejmank in https://github.com/GenomicDataInfrastructure/gdi-userportal-dataset-discovery-service/pull/27
 
 ### Changed
+
 - chore: replace private constructors by @brunopacheco1 in https://github.com/GenomicDataInfrastructure/gdi-userportal-dataset-discovery-service/pull/12
 
 ### Fixed
+
 - fix: handle correctly missing beacon access token and empty beacon re… by @brunopacheco1 in https://github.com/GenomicDataInfrastructure/gdi-userportal-dataset-discovery-service/pull/14
 - fix: #17 Retrieve Beacon Facets when logged-in by @brunopacheco1 in https://github.com/GenomicDataInfrastructure/gdi-userportal-dataset-discovery-service/pull/18
 - fix: fix beacon integration by @brunopacheco1 in https://github.com/GenomicDataInfrastructure/gdi-userportal-dataset-discovery-service/pull/25

CONTRIBUTING.md

@@ -30,12 +30,12 @@ community looks forward to your contributions. 🎉
 - [Code of Conduct](#code-of-conduct)
 - [I Have a Question](#i-have-a-question)
 - [I Want To Contribute](#i-want-to-contribute)
-    - [Reporting Bugs](#reporting-bugs)
-    - [Suggesting Enhancements](#suggesting-enhancements)
-    - [Your First Code Contribution](#your-first-code-contribution)
-    - [Improving The Documentation](#improving-the-documentation)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Suggesting Enhancements](#suggesting-enhancements)
+  - [Your First Code Contribution](#your-first-code-contribution)
+  - [Improving The Documentation](#improving-the-documentation)
 - [Styleguides](#styleguides)
-    - [Commit Messages](#commit-messages)
+  - [Commit Messages](#commit-messages)
 - [Join The Project Team](#join-the-project-team)
 
 ## Code of Conduct
@@ -91,11 +91,11 @@ following steps in advance to help us fix any potential bug as fast as possible.
 - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have
   discussed the issue.
 - Collect information about the bug:
-    - Stack trace (Traceback)
-    - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
-    - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
-    - Possibly your input and the output
-    - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
+  - Stack trace (Traceback)
+  - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
+  - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
+  - Possibly your input and the output
+  - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
 
 <!-- omit in toc -->
 

README.md

@@ -56,7 +56,7 @@ You can run your application in dev mode that enables live coding using:
 mvn compile quarkus:dev
 ```
 
-> **_NOTE:_**  Quarkus now ships with a Dev UI, which is available in dev mode only
+> **_NOTE:_** Quarkus now ships with a Dev UI, which is available in dev mode only
 > at http://localhost:8080/q/dev/.
 
 ## Packaging and running the application