Docker/mealie
Docker/mealie
1
0
Fork 0
mirror of https://github.com/mealie-recipes/mealie.git synced 2025-08-05 13:35:23 +02:00
Code Issues Releases Activity

fix: pre-commit autoupdate && pre-commit run --all-files (#3780)

Browse source
This commit is contained in:
Christian Clauss 2024-06-26 12:41:46 +02:00 • committed by GitHub
parent 5e0f8a4bf7
commit e2033b2d67
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
82 changed files with 94 additions and 98 deletions
Download patch file Download diff file Expand all files Collapse all files

9
frontend/components/README.md
View file

@ -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