fix(02-12): gate shared record navigation

- Wait for the shared-record banner before generated reads
- Keep the profile doorway in the navigation translation namespace
This commit is contained in:
Marc-André Bombeck committed 2026-08-06 14:35:02 +02:00
1 parent c42df8cbc3
commit a636a3b4c5
4 files changed
+4 -1

No files matched your search

@@ -356,6 +356,7 @@ test.describe.serial("scoped sharing browser journeys", () => {
await expect(banner).toHaveAttribute("data-record-kind", "shared");
await page.goto("/");
await expect(banner).toHaveAttribute("data-access-level", "manage");
const generatedRead = await page.evaluate(async () => {
const response = await fetch("/api/dashboard/summary");
return response.status;
+1
View File
@@ -341,6 +341,7 @@
},
"cycle": "Zyklus",
"labs": "Laborwerte",
"profile": "Profil",
"vorsorge": "Vorsorge",
"illness": "Krankheit",
"documents": "Dokumente",
+1
View File
@@ -341,6 +341,7 @@
},
"cycle": "Cycle",
"labs": "Labs",
"profile": "Profile",
"vorsorge": "Checkups",
"illness": "Illness",
"documents": "Documents",
+1 -1
View File
@@ -177,7 +177,7 @@ export const NAV_DESTINATIONS: ReadonlyArray<NavDestination> = [
href: "/profile",
sharedRecord: true,
sharedRecordOnly: true,
tKey: "settings.sections.anamnesis.title",
tKey: "nav.profile",
icon: ClipboardList,
tourId: "nav-profile",
},