From 3f0c7785b713f6024375cb18fd274e8e67fef59f Mon Sep 17 00:00:00 2001 From: Eva Marco Date: Fri, 14 Aug 2026 11:56:50 +0200 Subject: [PATCH] :bug: Fix catch validation errors on exception --- frontend/src/app/main/ui/static.cljs | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/frontend/src/app/main/ui/static.cljs b/frontend/src/app/main/ui/static.cljs index 9232c6598c..345e75a0da 100644 --- a/frontend/src/app/main/ui/static.cljs +++ b/frontend/src/app/main/ui/static.cljs @@ -542,7 +542,7 @@ (mf/with-effect [report type cause] (when (and (ex/exception? cause) - (not (contains? #{:not-found :authentication} type))) + (not (contains? #{:not-found :authentication :validation} type))) (errors/submit-report :event-name "exception-page" :report report :hint (ex/get-hint cause)))) @@ -554,6 +554,14 @@ :authentication [:> not-found* {}] + ;; A malformed/invalid resource identifier (e.g. a broken file-id + ;; in the URL) surfaces as a generic :validation error rather than + ;; :not-found. By the time it reaches here it has no more specific + ;; handling (see `handle-error :validation`'s fallback in errors.cljs), + ;; so treat it the same as "this page doesn't exist". + :validation + [:> not-found* {}] + :bad-gateway [:> bad-gateway* props]