<details>

<summary>Click to view screenshots</summary>

<summary>Click to view screenshots</summary>

</details>

</details>

on:

pull_request:

paths:

-'snippets/**'

-"snippets/**"

jobs:

check-snippets:

on:

pull_request:

branches:

-'**'

-"**"

jobs:

pre-commit-checks:

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!

- An`example` segement, containing one or more examples of use

Example in #"diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055-52-53-0" data-selected="false" role="gridcell" tabindex="-1" valign="top">

functionexample(x) {

return x*2;

return x*2;

}

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.

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 ?**

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:

---

---

```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:

To test that your snippets are formatted correctly use the`snippets:check` script:

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.

---

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

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.

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:

/snippets

|- python

|- file-handling

|- list-manipulation

|- ....

|- python

|- file-handling

|- list-manipulation

|- ....

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.

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:

We do**NOT** aim to be:

- a component library

- a documentation

- a documentation

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.

}

],

"dictionaries": ["workspace"],

"ignorePaths": [

"node_modules",

"dist",

"coverage",

]

"ignorePaths": ["node_modules","dist","coverage","public"]

}

margin-left:2.25em;

}

.search-field:hover, .search-field:hover* {

.search-field:hover,

.search-field:hover* {

cursor: pointer;

}

margin-left:1.5rem;

}

.sublanguage__button{

.sublanguage__button{

margin-left: auto;

display: flex;

align-items: center;

max-height:90vh;

overflow-y: auto;

overflow-x: hidden;

padding:0.5rem1rem1rem1rem;

padding:0.5rem1rem1rem1rem;

align-content: start;

}