[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

.devcontainer/Dockerfile

@@ -2,4 +2,4 @@
 ARG VARIANT=16-bullseye
 FROM mcr.microsoft.com/vscode/devcontainers/typescript-node:0-${VARIANT}
 
-RUN sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin
+RUN sh -c "$(curl --location https://taskfile.dev/install.sh)" -- -d -b ~/.local/bin

.github/pull_request_template.md

@@ -69,4 +69,4 @@ _(REQUIRED)_
 -->
 
 ```release-note
-```
+```

.github/workflows/publish.yaml

@@ -25,5 +25,3 @@
 #       tag: nightly
 #     secrets:
 #       GH_TOKEN: ${{ secrets.CR_PAT }}
-
-

.github/workflows/pull-requests.yaml

@@ -12,4 +12,4 @@ jobs:
 
   frontend-tests:
     name: "Frontend and End-to-End Tests"
-    uses: ./.github/workflows/partial-frontend.yaml
+    uses: ./.github/workflows/partial-frontend.yaml

.github/workflows/tag.yaml

@@ -80,4 +80,4 @@
 #         env:
 #           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 #           CONFIG_FILE: docs/mkdocs.yml
-#           EXTRA_PACKAGES: build-base
+#           EXTRA_PACKAGES: build-base

.gitignore

@@ -54,4 +54,4 @@ dist/
 # Nuxt Publish Dir
 backend/app/api/static/public/*
 !backend/app/api/static/public/.gitkeep
-backend/api
+backend/api

.scaffold/model/templates/model.go

@@ -37,4 +37,4 @@ func ({{ .Scaffold.model }}) Indexes() []ent.Index {
 	return []ent.Index{
 		// index.Fields("token"),
 	}
-}
+}

.vscode/launch.json

@@ -44,4 +44,4 @@
               }
         }
     ]
-}
+}

CONTRIBUTING.md

@@ -54,4 +54,4 @@ start command `task: ui:dev`
 
 Create a new tag in GitHub with the version number vX.X.X. This will trigger a new release to be created.
 
-Test -> Goreleaser -> Publish Release -> Trigger Docker Builds -> Deploy Docs + Fly.io Demo
+Test -> Goreleaser -> Publish Release -> Trigger Docker Builds -> Deploy Docs + Fly.io Demo

LICENSE

@@ -658,4 +658,4 @@ specific requirements.
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
 For more information on this, and how to apply and follow the GNU AGPL, see
-<https://www.gnu.org/licenses/>.
+<https://www.gnu.org/licenses/>.

README.md

@@ -22,7 +22,7 @@ Big thanks to the original author @hay-kot.
 [Configuration & Docker Compose](https://hay-kot.github.io/homebox/quick-start)
 
 ```bash
-# If using the rootless image, ensure data 
+# If using the rootless image, ensure data
 # folder has correct permissions
 mkdir -p /path/to/data/folder
 chown 65532:65532 -R /path/to/data/folder

SECURITY.md

@@ -6,4 +6,4 @@ Since this software is still considered beta/WIP support is always only given fo
 
 ## Reporting a Vulnerability
 
-Please open a normal public issue if you have any security related concerns.
+Please open a normal public issue if you have any security related concerns.

backend/.golangci.yml

@@ -71,4 +71,4 @@ issues:
   exclude-use-default: false
   fix: true
   exclude-dirs:
-    - internal/data/ent.*
+    - internal/data/ent.*

backend/app/api/static/docs/swagger.json

@@ -3038,4 +3038,4 @@
             "in": "header"
         }
     }
-}
+}

backend/internal/core/services/reporting/.testdata/import/fields.csv

@@ -2,4 +2,3 @@ HB.location,HB.name,HB.quantity,HB.description,HB.field.Custom Field 1,HB.field.
 loc,Item 1,1,Description 1,Value 1[1],Value 1[2],Value 1[3]
 loc,Item 2,2,Description 2,Value 2[1],Value 2[2],Value 2[3]
 loc,Item 3,3,Description 3,Value 3[1],Value 3[2],Value 3[3]
-

backend/internal/core/services/reporting/.testdata/import/minimal.csv

@@ -1,4 +1,4 @@
 HB.location,HB.name,HB.quantity,HB.description
 loc,Item 1,1,Description 1
 loc,Item 2,2,Description 2
-loc,Item 3,3,Description 3
+loc,Item 3,3,Description 3

backend/internal/core/services/reporting/.testdata/import/types.csv

@@ -1,4 +1,4 @@
 HB.name,HB.asset_id,HB.location,HB.labels
 Item 1,1,Path / To / Location 1,L1 ; L2 ; L3
 Item 2,000-002,Path /To/ Location 2,L1;L2;L3
-Item 3,1000-003,Path / To /Location 3  ,   L1;L2;   L3
+Item 3,1000-003,Path / To /Location 3  ,   L1;L2;   L3

backend/internal/data/migrations/migrations/20221205230404_drop_document_tokens.sql

@@ -2,4 +2,4 @@
 PRAGMA foreign_keys = off;
 DROP TABLE `document_tokens`;
 -- enable back the enforcement of foreign-keys constraints
-PRAGMA foreign_keys = on;
+PRAGMA foreign_keys = on;

backend/internal/data/repo/repo_locations.go

@@ -280,14 +280,14 @@ func (r *LocationRepository) PathForLoc(ctx context.Context, groupID, locID uuid
 			FROM locations
 			WHERE id = ?
 			AND group_locations = ?
-			
+
 			UNION ALL
-			
+
 			SELECT loc.id, loc.name, loc.location_children
 			FROM locations loc
 			JOIN location_path lp ON loc.id = lp.location_children
 		)
-		
+
 		SELECT id, name
 		FROM location_path`,
 		locID, groupID)
@@ -337,7 +337,7 @@ func (r *LocationRepository) Tree(ctx context.Context, groupID uuid.UUID, tq Tre
 			FROM    locations
 			WHERE   location_children IS NULL
 			AND     group_locations = ?
-		
+
 			UNION ALL
 			SELECT  c.id,
 					c.NAME,
@@ -362,9 +362,9 @@ func (r *LocationRepository) Tree(ctx context.Context, groupID uuid.UUID, tq Tre
 				FROM    items
 				WHERE   item_children IS NULL
 				AND     location_items IN (SELECT id FROM location_tree)
-	
+
 				UNION ALL
-	
+
 				SELECT  c.id,
 						c.NAME,
 						c.item_children AS parent_id,

backend/pkgs/mailer/test-mailer-template.json

@@ -4,4 +4,4 @@
     "username": "",
     "password": "",
     "from": ""
-}
+}

docs/docs/api/openapi-2.0.json

@@ -3038,4 +3038,4 @@
             "in": "header"
         }
     }
-}
+}

docs/docs/assets/stylesheets/extras.css

@@ -22,4 +22,4 @@ th {
 
 .md-button {
   padding: 0.2rem 0.75rem !important;
-}
+}

docs/docs/build.md

@@ -12,4 +12,4 @@ TODO
 
 ## Running
 
-TODO
+TODO

docs/docs/index.md

@@ -53,4 +53,4 @@ That's a fair point. If your needs can be fulfilled by a Spreadsheet, I'd sugges
 
 ### Snipe-It?
 
-Snipe-It is the gold standard for IT management. If your use-case is to manage consumables and IT physical infrastructure, I highly suggest you look at Snipe-It over Homebox, it's just more purpose built for that use case. Homebox is, in contrast, purpose built for the home user, which means that we try to focus on keeping things simple and easy to use. Lowering the friction for creating items and managing them is a key goal of Homebox which means you lose out on some of the more advanced features. In most cases, this is a good trade-off.
+Snipe-It is the gold standard for IT management. If your use-case is to manage consumables and IT physical infrastructure, I highly suggest you look at Snipe-It over Homebox, it's just more purpose built for that use case. Homebox is, in contrast, purpose built for the home user, which means that we try to focus on keeping things simple and easy to use. Lowering the friction for creating items and managing them is a key goal of Homebox which means you lose out on some of the more advanced features. In most cases, this is a good trade-off.

docs/requirements.txt

@@ -1 +1 @@
-mkdocs-material==9.5.12
+mkdocs-material==9.5.12

frontend/.nuxtignore

@@ -1 +1 @@
-pages/**/*.ts
+pages/**/*.ts

frontend/assets/css/main.css

@@ -23,4 +23,4 @@
 
 ::-webkit-scrollbar-thumb:hover {
   background-color: #9B9B9B;
-}
+}

frontend/global.d.ts

@@ -1 +1 @@
-/// <reference types="unplugin-icons/types/vue" />
+/// <reference types="unplugin-icons/types/vue" />