blob: 51505a1b8e22d84da184fb96007cbd6f3b390042 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
# How to update/change recipes
If you want to improve or update an existing recipe, please follow this guide.
## 1. Implement your updates
We highly suggest that you implement and test your updates to the recipe inside Ferdium before implementing them into the recipe repository. This will save you time on debugging and repackaging the recipe later.
You can find the recipe source Ferdium uses at:
* Mac: `~/Library/Application Support/Ferdium/recipes/<recipe id>/`
* Windows: `%appdata%/Ferdium/recipes/<recipe id>/`
* Linux: `~/.config/Ferdium/recipes/<recipe id>`
> If you can't find the recipe's folder, please make sure that you have created a service inside Ferdium with that recipe - otherwise Ferdium will not load it into the folder
After changing the files in that folder, you can reload the service inside Ferdium using `CTRL/CMD + R`.
## 2. Setting up the recipe repository
Simply fork https://github.com/ferdium/ferdium-recipes. You may also want to clone the repository to your computer to edit it locally.
## 3. Updating the recipe inside the repository
Simply add your changes to the recipe inside this repository.
## 4. Updating the version number
You'll need to increase the version number inside recipe's `package.json`.
Ferdium uses this version to determine if it should update the local copy of the recipe. If you do not increase the version number, no Ferdium user will get your updated recipe 😔
## 5. Running the validation checks
This might be the __most important step__ of this guide. You'll need to run the `pnpm lint:fix && pnpm reformat-files && pnpm package` command to ensure that all validation checks are run.
## 6. Commit your changes and create a PR to <https://github.com/ferdium/ferdium-recipes>
|