Frontend: Cookie-Handling zentralisiert #308
Labels
No labels
component/backend
component/docs
component/e2e
component/frontend
component/infra
component/keycloak
prio/high
prio/low
prio/medium
type/bug
type/chore
type/feature
type/refactor
type/test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
WompSchmiede/FamilienFeierPlaner#308
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cookie-Operationen (setzen/lesen/loeschen) waren auf 10+ Dateien verteilt mit duplizierten Optionen und Magic Strings. Zentralisierung in:
frontend/src/lib/config/cookies.ts— COOKIE_NAMES, Option-Presets, MAX_AGESfrontend/src/lib/utils/client-cookie.ts— getCookie/setCookie/deleteCookie fuer document.cookiefrontend/src/lib/utils/server-cookie.ts— setSessionTokens/clearSession/setUserInfo/setOauthFlow/clearOauthFlow fuer event.cookiesZusaetzlich:
fetch2-Import incallback/+server.tswiederhergestellt (wurde versehentlich durchfetchersetzt, brach E2E-Tests)fetch2-convention.test.tspruft, dass Server-Routenfetch2stattfetchnutzenGeaenderte Dateien (11):
hooks.server.ts, callback/+server.ts, login/+server.ts, logout/+server.ts, session-touch/+server.ts, +page.server.ts, app/+layout.server.ts, app/+layout.svelte, lib/server/auth.ts, i18n.svelte.ts, consent-dialog.svelte
niboer referenced this issue2026-07-19 20:45:03 +00:00