From eecdf75f5e17eefff3e6f7b0e02ba6b4e5ce8941 Mon Sep 17 00:00:00 2001 From: Dat Vu Date: Thu, 19 Mar 2026 17:13:31 +0700 Subject: [PATCH] TF-4384 Add ADR-0074 Resolve label refresh 404 by introducing explicit labelId (#4387) --- ...resh-404-with-explicit-label-id-routing.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/adr/0074-fix-label-refresh-404-with-explicit-label-id-routing.md diff --git a/docs/adr/0074-fix-label-refresh-404-with-explicit-label-id-routing.md b/docs/adr/0074-fix-label-refresh-404-with-explicit-label-id-routing.md new file mode 100644 index 000000000..014978da7 --- /dev/null +++ b/docs/adr/0074-fix-label-refresh-404-with-explicit-label-id-routing.md @@ -0,0 +1,25 @@ +# 0074 - Fix 404 on Label Refresh by Introducing Explicit `labelId` in Web Routing + +Date: 2026-03-18 + +## Status + +Proposed + +## Context + +Refreshing a label view on web results in a 404 error because label IDs are incorrectly interpreted as `mailboxId` from the URL. + +## Decision + +Introduce an explicit `labelId` query parameter to distinguish labels from mailboxes in routing. + +* Mailbox: `/dashboard?context=` +* Label: `/dashboard?labelId=` + +## Consequences + +* ✅ Fixes 404 on refresh +* ✅ Enables correct deep linking and bookmarking +* ⚠️ Requires updating routing logic and URL generation +* ⚠️ Legacy URLs must be handled via fallback logic \ No newline at end of file