Run prettier formatter and convert to LF

.github/pull_request_template.md

@@ -39,8 +39,8 @@ Closes #
 <!-- If your changes affect visuals, please include screenshots. -->
 
 <details> 
-<summary>Click to view screenshots</summary> 
+<summary>Click to view screenshots</summary>
 
-<!-- Add your screenshots here --> 
+<!-- Add your screenshots here -->
 
-</details>
+</details>

.github/workflows/check-snippets.yml

@@ -3,7 +3,7 @@ name: Checks snippets syntax
 on:
   pull_request:
     paths:
-      - 'snippets/**'
+      - "snippets/**"
 
 jobs:
   check-snippets:

.github/workflows/pre-commit-checks.yml

@@ -3,7 +3,7 @@ name: Pre-commit checks
 on:
   pull_request:
     branches:
-      - '**'
+      - "**"
 
 jobs:
   pre-commit-checks:

CODE_OF_CONDUCT.md

@@ -35,4 +35,3 @@ No bots are allowed within the QuickSnip community without prior written permiss
 #### Final Notes
 
 This code of conduct is inspired by [FreeCodeCamp’s approach](https://www.freecodecamp.org/news/code-of-conduct), emphasizing clarity and friendliness. Let’s work together to make QuickSnip a supportive and productive space for all developers!
-

CONTRIBUTING.md

@@ -50,20 +50,22 @@ tags: number,currency
 - An `example` segement, containing one or more examples of use
 
 Example in javascript:
+
 ```js
 function example(x) {
-    return x * 2;
+  return x * 2;
 }
 
 // Usage:
-example(5) // Returns: 10
+example(5); // Returns: 10
 ```
 
 If your function doesn't return anything just show how to use it. If the result of your function is too complicated to be expressed in a single comment, your snippet is probably too complex to begin with.
 
 ### Snippet boundaries
 
 To ensure your snippet isn’t refused, consider these questions:
+
 - **Does the standard library of my language provide an easy way of doing this ?**
 - **Does that snippet not have a real, and practical use case ?**
 - **Could it be split into separate parts to be better understood ?**
@@ -79,23 +81,23 @@ If any answer is yes, then your snippet will most likely get rejected.
 1. **Ensure your snippet match [guidelines](#snippets-guidelines)**
 
 2. **Navigate to the relevant folder:**
-  
-    - Go to the `/snippets` folder in the root directory.
-    - Locate the folder for the programming language of your snippet, such as `javascript` or `python`.
+
+   - Go to the `/snippets` folder in the root directory.
+   - Locate the folder for the programming language of your snippet, such as `javascript` or `python`.
 
 3. **Choose the correct category:**
 
-    - Within the language folder, find the relevant category folder for your snippet.
-    - If no suitable category exists, refer to [Adding a New Category](#adding-a-new-category).
+   - Within the language folder, find the relevant category folder for your snippet.
+   - If no suitable category exists, refer to [Adding a New Category](#adding-a-new-category).
 
 4. **Create a markdown file:**
 
-    - Create a new file with a `.md` extension.
-    - Name the file appropriately, keeping it descriptive and concise.
+   - Create a new file with a `.md` extension.
+   - Name the file appropriately, keeping it descriptive and concise.
 
 5. **Add your snippet:**
 
-    - Use the following format to structure your snippet:
+   - Use the following format to structure your snippet:
 
 ````md
 ---
@@ -121,39 +123,46 @@ tags: date,format
 ---
 
 ```js
-const formatDate = (date) => date.toISOString().split('T')[0];
+const formatDate = (date) => date.toISOString().split("T")[0];
 
 // Usage:
 console.log(formatDate(new Date())); // Output: '2024-12-10'
 ```
 ````
 
 6. **Use syntax highlighting:**
-    - Enclose your code with triple backticks (```).
-    - Specify the language after the first set of backticks for syntax highlighting.
+
+   - Enclose your code with triple backticks (```).
+   - Specify the language after the first set of backticks for syntax highlighting.
 
 7. **Test your snippet:**
+
    - Ensure your code runs as expected. \
-        To test that your snippets are formatted correctly use the `snippets:check` script:
-        ```
-        $ npm run snippets:check
-        ```
-        It will return nothing if they are well formatted, otherwise it will tell you what the error is.
-
-        ---
-        To preview the snippets, start the vite server using:
-        ```
-        $ npm run dev
-        ```
-        It will use HMR to update the snippets in the `/public` folder, making them available to the frontend.
+      To test that your snippets are formatted correctly use the `snippets:check` script:
+
+     ```
+     $ npm run snippets:check
+     ```
+
+     It will return nothing if they are well formatted, otherwise it will tell you what the error is.
+
+     ***
+
+     To preview the snippets, start the vite server using:
+
+     ```
+     $ npm run dev
+     ```
+
+     It will use HMR to update the snippets in the `/public` folder, making them available to the frontend.
 
 Expected file structure:
 
 ```md
 /snippets
-  |- language
-    |- category-name
-      |- your-snippet-here.md
+|- language
+|- category-name
+|- your-snippet-here.md
 ```
 
 > Please do **NOT** add or edit anything in `/public` folder. It will be used for consolidating snippets.
@@ -164,7 +173,7 @@ If you’d like to refine or improve an existing snippet:
 
 1. **Add a `contributors` field:**
 
-    - Include your GitHub username under the `contributors` field in the metadata section.
+   - Include your GitHub username under the `contributors` field in the metadata section.
 
 ````md
 ---
@@ -182,15 +191,15 @@ Updated code here
 
 2. **Credit all contributors:**
 
-    - If contributors already exist, add your username separated by a comma
+   - If contributors already exist, add your username separated by a comma
 
 ```md
 contributors: contributor1, contributor2, your-github-username
 ```
 
 3. **Document changes:**
 
-    - Clearly indicate what you updated and why in your pull request description.
+   - Clearly indicate what you updated and why in your pull request description.
 
 > We want to make sure that original author and contributor(s) are credited for their work.
 
@@ -200,21 +209,21 @@ If your snippet doesn’t fit into any existing category, you can create a new o
 
 1. **Create a new category folder:**
 
-    - In the relevant language directory, add a new folder.
-    - Use a lowercase name with hyphens for separation (e.g., `file-handling`).
+   - In the relevant language directory, add a new folder.
+   - Use a lowercase name with hyphens for separation (e.g., `file-handling`).
 
 2. **Add snippets:**
 
-    - Follow the [Adding a New Snippet](#adding-a-new-snippet) instructions.
+   - Follow the [Adding a New Snippet](#adding-a-new-snippet) instructions.
 
 Example structure:
 
 ```md
 /snippets
-  |- python
-    |- file-handling
-    |- list-manipulation
-    |- ....
+|- python
+|- file-handling
+|- list-manipulation
+|- ....
 ```
 
 ### Adding a New Language
@@ -223,21 +232,21 @@ If you want to introduce a new programming language, here's how to do it:
 
 1. **Create a language folder:**
 
-    - Add a new folder under the `snippets` directory.
-    - Name it after the language in lowercase (e.g., `go`, `ruby`).
+   - Add a new folder under the `snippets` directory.
+   - Name it after the language in lowercase (e.g., `go`, `ruby`).
 
 2. **Add categories and snippets:**
 
-    - Follow the [Adding a New Snippet](#adding-a-new-snippet) and [Adding a New Category](#adding-a-new-category) guidelines.
+   - Follow the [Adding a New Snippet](#adding-a-new-snippet) and [Adding a New Category](#adding-a-new-category) guidelines.
 
-4. **Include an icon:**
+3. **Include an icon:**
 
-    - Add an `icon.svg` file (50x50px) in the same language folder.
-    - Use tools like [Resize SVG](https://www.iloveimg.com/resize-image/resize-svg) to ensure the correct size.
+   - Add an `icon.svg` file (50x50px) in the same language folder.
+   - Use tools like [Resize SVG](https://www.iloveimg.com/resize-image/resize-svg) to ensure the correct size.
 
-5. **Double-check your work:**
+4. **Double-check your work:**
 
-    - Verify that everything is structured correctly and displays as intended.
+   - Verify that everything is structured correctly and displays as intended.
 
 ---
 
@@ -252,6 +261,7 @@ $ npm run snippets:check
 It will return nothing if they are well formatted, otherwise it will tell you what the error is.
 
 ---
+
 To preview the snippets, you need to consolidate them, use the following script:
 
 ```

VISION.md

@@ -21,7 +21,7 @@ QuickSnip is an open-source tool designed for developers who want to organize, s
 We do **NOT** aim to be:
 
 - a component library
-- a documentation 
+- a documentation
 
 ## QuickSnip Roadmap
 
@@ -52,4 +52,4 @@ This roadmap outlines our current vision for QuickSnip and may evolve based on u
 
 QuickSnip aims to become the preferred platform for developers to store, retrieve, and collaborate on code snippets.
 
-Explore our [GitHub Releases](https://github.com/dostonnabotov/quicksnip/releases) for updates and join us on this journey.
+Explore our [GitHub Releases](https://github.com/dostonnabotov/quicksnip/releases) for updates and join us on this journey.

cspell.json

@@ -8,10 +8,5 @@
     }
   ],
   "dictionaries": ["workspace"],
-  "ignorePaths": [
-    "node_modules",
-    "dist",
-    "coverage",
-    "public"
-  ]
+  "ignorePaths": ["node_modules", "dist", "coverage", "public"]
 }

src/styles/main.css

@@ -325,7 +325,8 @@ abbr {
   margin-left: 2.25em;
 }
 
-.search-field:hover, .search-field:hover * {
+.search-field:hover,
+.search-field:hover * {
   cursor: pointer;
 }
 
@@ -445,7 +446,7 @@ abbr {
   margin-left: 1.5rem;
 }
 
-.sublanguage__button{
+.sublanguage__button {
   margin-left: auto;
   display: flex;
   align-items: center;
@@ -615,7 +616,7 @@ abbr {
   max-height: 90vh;
   overflow-y: auto;
   overflow-x: hidden;
-  padding: 0.5rem 1rem 1rem 1rem;  
+  padding: 0.5rem 1rem 1rem 1rem;
   align-content: start;
 }