fix: pre-commit autoupdate && pre-commit run --all-files

.dockerignore

@@ -26,7 +26,7 @@ venv
 */node_modules
 */dist
 */data/db
-*/mealie/test 
+*/mealie/test
 */mealie/.temp
 
 model.crfmodel

.gitattributes

@@ -1,2 +1,2 @@
 *.css linguist-detectable=false
-*.html linguist-detectable=false
+*.html linguist-detectable=false

.github/DISCUSSION_TEMPLATE/oauth-provider-example.yaml

@@ -5,5 +5,5 @@ body:
   attributes:
     label: Configuration Example
     description: Add your example configuration. You can provide code blocks, screenshots, and links.
-  validations: 
+  validations:
     required: true

.github/pull_request_template.md

@@ -1,12 +1,12 @@
 <!--
   This template provides some ideas of things to include in your PR description.
-  
+
   To start, try providing a short summary of your changes in the Title above. We follow Conventional Commits syntax, please ensure your title is prefixed with one of:
   - `feat: `
   - `fix: `
   - `docs: `
   - `chore: `
-  
+
   If a section of the PR template does not apply to this PR, then delete that section.
 
   PLEASE READ:

.pre-commit-config.yaml

@@ -1,6 +1,6 @@
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v2.3.0
+    rev: v4.6.0
     hooks:
       - id: check-yaml
         exclude: "mkdocs.yml"
@@ -12,6 +12,6 @@ repos:
         exclude: ^tests/data/
   - repo: https://github.com/astral-sh/ruff-pre-commit
     # Ruff version.
-    rev: v0.4.3
+    rev: v0.4.10
     hooks:
       - id: ruff-format

alembic/README

@@ -1 +1 @@
-Generic single-database configuration.
+Generic single-database configuration.

dev/code-generation/templates/test_data.py.j2

@@ -4,4 +4,4 @@ CWD = Path(__file__).parent
 
 {% for f in data.children %}
 {{ f.var }} = CWD / "{{ f.path }}"
-{% endfor %}
+{% endfor %}

dev/data/templates/recipes.md

@@ -6,11 +6,11 @@
 {{ recipe.description }}
 
 ## Ingredients
-{% for ingredient in recipe.recipeIngredient %} 
+{% for ingredient in recipe.recipeIngredient %}
 - [ ] {{ ingredient }} {% endfor %}
 
 ## Instructions
-{% for step in recipe.recipeInstructions %} 
+{% for step in recipe.recipeInstructions %}
 - [ ] {{ step.text }} {% endfor %}
 
 {% for note in recipe.notes %}
@@ -21,4 +21,4 @@
 
 Tags: {{ recipe.tags }}
 Categories: {{ recipe.categories }}
-Original URL: {{ recipe.orgURL }}
+Original URL: {{ recipe.orgURL }}

docs/docs/assets/other/n8n/n8n-mealie-backup.json

@@ -383,4 +383,4 @@
   },
   "id": "whloxeXkdBWWi2Uj",
   "tags": []
-}
+}

docs/docs/contributors/guides/ingredient-parser.md

@@ -1,20 +1,19 @@
 # Improving the Ingredient Parser
 
-Mealie uses Conditional Random Fields (CRFs) for parsing and processing ingredients. The model used for ingredients is based off a data set of over 100,000 ingredients from a dataset compiled by the New York Times. I believe that the model used is sufficient enough to handle most of the ingredients, therefore, more data to train the model won't necessarily help improve the model. 
+Mealie uses Conditional Random Fields (CRFs) for parsing and processing ingredients. The model used for ingredients is based off a data set of over 100,000 ingredients from a dataset compiled by the New York Times. I believe that the model used is sufficient enough to handle most of the ingredients, therefore, more data to train the model won't necessarily help improve the model.
 
 ## Improving The CRF Parser
 
-To improve results with the model, you'll likely need to focus on improving the tokenization and parsing of the original string to aid the model in determine what the ingredient is. Data science is not my forte, but I have done some tokenization to improve the model. You can find that code under `/mealie/services/parser_services/crfpp` along with some other utility functions to aid in the tokenization and processing of ingredient strings. 
+To improve results with the model, you'll likely need to focus on improving the tokenization and parsing of the original string to aid the model in determine what the ingredient is. Data science is not my forte, but I have done some tokenization to improve the model. You can find that code under `/mealie/services/parser_services/crfpp` along with some other utility functions to aid in the tokenization and processing of ingredient strings.
 
 The best way to test on improving the parser is to register additional test cases in  `/mealie/tests/unit_tests/test_crfpp_parser.py` and run the test after making changes to the tokenizer. Note that the test cases DO NOT run in the CI environment, therefore you will need to have CRF++ installed on your machine. If you're using a Mac the easiest way to do this is through brew.
 
-When submitting a PR to improve the parser it is important to provide your test cases, the problem you were trying to solve, and the results of the changes you made. As the tests don't run in CI, not providing these details may delay your PR from being merged. 
+When submitting a PR to improve the parser it is important to provide your test cases, the problem you were trying to solve, and the results of the changes you made. As the tests don't run in CI, not providing these details may delay your PR from being merged.
 
 ## Alternative Parsers
-Alternatively, you can register a new parser by fulfilling the `ABCIngredientParser` interface. Satisfying this single method interface allows us to register additional parsing strategies at runtime and gives the user several options when trying to parse a recipe. 
+Alternatively, you can register a new parser by fulfilling the `ABCIngredientParser` interface. Satisfying this single method interface allows us to register additional parsing strategies at runtime and gives the user several options when trying to parse a recipe.
 
 
 ## Links
 - [Pretrained Model](https://github.com/mealie-recipes/mealie-nlp-model)
 - [CRF++ (Forked)](https://github.com/hay-kot/crfpp)
-

docs/docs/contributors/non-coders.md

@@ -9,8 +9,8 @@ We love your input! We want to make contributing to this project as easy and tra
 - Becoming a maintainer
 - Help translate to a new language or improve current translations
 
-[Remember to join the Discord and stay in touch with other developers working on the project](https://discord.gg/QuStdQGSGK)! 
+[Remember to join the Discord and stay in touch with other developers working on the project](https://discord.gg/QuStdQGSGK)!
 
-Additionally, you can buy me a coffee and support the project. When I get financial support it helps me know that there's real interest in the project and that it's worth the time to keep developing. 
+Additionally, you can buy me a coffee and support the project. When I get financial support it helps me know that there's real interest in the project and that it's worth the time to keep developing.
 
-<a href="https://www.buymeacoffee.com/haykot" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-green.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a>
+<a href="https://www.buymeacoffee.com/haykot" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-green.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a>

docs/docs/documentation/community-guide/bulk-url-import.md

@@ -93,4 +93,3 @@ mealie_url="http://localhost:9000"
 token = authentication(mail, password, mealie_url)
 import_from_file(input_file, token, mealie_url)
 ```
-

frontend/.prettierrc

@@ -6,4 +6,4 @@
   "printWidth": 120,
   "arrowParens": "always",
   "eslintIntegration": true
-}
+}

frontend/components/Domain/User/UserProfileLinkCard.vue

@@ -53,4 +53,3 @@ export default defineComponent({
   },
 });
 </script>
-

frontend/components/README.md

@@ -1,7 +1,7 @@
 # Components Folder Guide
 
 ## Domain Components
-Domain Components are specific to the domain or section of a website. For example if you have an admin page and a user page that have specific, unshared elements. These can be placed in the Domain/Admin folder. 
+Domain Components are specific to the domain or section of a website. For example if you have an admin page and a user page that have specific, unshared elements. These can be placed in the Domain/Admin folder.
 
 **Rules**
 - Components should be prefixed with their domain name
@@ -19,8 +19,8 @@ This folder is for widely reused components that provide little functionality an
 The layout folder is for reusable components that are specifically **only** used in the layouts for the Nuxt Application. They may take props or may not. They should be larger layout style components that don't have wide the ability to be widely reused in the application.
 
 **Rules:**
-- Layout folder should not have a subfolder 
-- If they take props they should start with a 'App' Prefix. 
+- Layout folder should not have a subfolder
+- If they take props they should start with a 'App' Prefix.
   - Examples: AppSidebar, AppHeader, AppFooter.
 - If they do not they should begin with the 'The' prefix
   - Examples: TheSidebar, TheHeader, TheFooter.
@@ -29,7 +29,6 @@ The layout folder is for reusable components that are specifically **only** used
 The Page folder is dedicated to 'single-use' component to break up large amounts on content in the pages themselves. A good examples of this is breaking your landing page into separate sections to make it more readable and less monolithic. Page components typically consume other components.
 
 **Rules:**
-- These are *last resort* components. Only to be used when the page becomes unmanageable. 
+- These are *last resort* components. Only to be used when the page becomes unmanageable.
 - Page components should be prefixed with their page name
   - Examples: HomeAbout, HomeContact, ClientProfile
-

frontend/components/global/DevDumpJson.vue

@@ -22,4 +22,4 @@ export default defineComponent({
     };
   },
 });
-</script>
+</script>

frontend/composables/recipe-page/use-extract-ingredient-references.ts

@@ -57,4 +57,4 @@ export function useExtractIngredientReferences(recipeIngredients: RecipeIngredie
 
     return new Set<string>(allMatchedIngredientIds)
 
-}
+}

frontend/lang/dateTimeFormats/af-ZA.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ar-SA.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/bg-BG.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ca-ES.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/cs-CZ.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/el-GR.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/en-GB.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/es-ES.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/fi-FI.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/fr-CA.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/fr-FR.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/he-IL.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/hu-HU.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ja-JP.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ko-KR.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/nl-NL.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/no-NO.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/pl-PL.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/pt-BR.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/pt-PT.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ro-RO.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ru-RU.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/sk-SK.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/sr-SP.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/sv-SE.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/tr-TR.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/vi-VN.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/zh-CN.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/zh-TW.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}