mirror of
https://github.com/immich-app/immich
synced 2026-08-29 13:15:45 +00:00
* implement updated rename tag feature * Fix tag update handler * Ensure toast displays updated tag name * Ensure toast displays updated tag name * Handle updates to tag closure table, prevent slash in API filename, test case updates * delete child tags on parent delete * Update frontend for better handling of nested tags * pr checklist fixes * fix unit test for tag controller * Hide path for top-level tags * regenerate SQL files * name updates optional for tag update operations * e2e tests for new tag api changes * changes from code review, additional test coverage * test fixes, web component refactor * test assets * test asset updates * open-api rebuild * update unit tests * fix tag dto tests * Update web/src/lib/modals/TagEditModal.svelte Fix missing color bug Co-authored-by: Ray <3608878+Pecacheu@users.noreply.github.com> * fix tag e2e test * remove closure table bug fixes * remove nullish from tag name update schema * regenerate openapi and sql * fix test and e2e test * simplify tag repository update process * minor fix and sql regenerate * fix tests, regen open-api, update dto * Remove unused function * Remove accidental test asset ref * re-add test assets * pin submodule to main branch commit * Update test cases based on feedback * Server fixes based on feedback * regenerate sql --------- Co-authored-by: Ray <3608878+Pecacheu@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| bin | ||
| src | ||
| static | ||
| tests | ||
| .browserslistrc | ||
| .dockerignore | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| eslint.config.js | ||
| lint-env.js | ||
| mise.toml | ||
| package.json | ||
| README.md | ||
| svelte.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
Immich web project
This project uses the SvelteKit web framework. Please refer to the SvelteKit docs for information on getting started as a contributor to this project. In particular, it will help you navigate the project's code if you understand the basics of SvelteKit routing.
When developing locally, you will run a SvelteKit Node.js server. When this project is deployed to production, it is built as a SPA and deployed as part of the server project.