🎉 Add sentry integration (frontend).

frontend/src/app/main/ui.cljs

@@ -6,20 +6,16 @@
 
 (ns app.main.ui
   (:require
-   [app.common.exceptions :as ex]
    [app.common.spec :as us]
    [app.config :as cf]
-   [app.main.data.events :as ev]
-   [app.main.data.messages :as dm]
-   [app.main.data.users :as du]
    [app.main.refs :as refs]
-   [app.main.store :as st]
    [app.main.ui.auth :refer [auth]]
    [app.main.ui.auth.verify-token :refer [verify-token]]
    [app.main.ui.components.fullscreen :as fs]
    [app.main.ui.context :as ctx]
    [app.main.ui.cursors :as c]
    [app.main.ui.dashboard :refer [dashboard]]
+   [app.main.ui.errors]
    [app.main.ui.icons :as i]
    [app.main.ui.messages :as msgs]
    [app.main.ui.onboarding]
@@ -28,11 +24,7 @@
    [app.main.ui.static :as static]
    [app.main.ui.viewer :as viewer]
    [app.main.ui.workspace :as workspace]
-   [app.util.timers :as ts]
-   [cljs.pprint :refer [pprint]]
    [cljs.spec.alpha :as s]
-   [cuerdas.core :as str]
-   [expound.alpha :as expound]
    [potok.core :as ptk]
    [rumext.alpha :as mf]))
 
@@ -199,143 +191,3 @@
         [:& msgs/notifications]
         (when route
           [:& main-page {:route route}])])]))
-
-;; --- Error Handling
-
-;; That are special case server-errors that should be treated
-;; differently.
-(derive :not-found ::exceptional-state)
-(derive :bad-gateway ::exceptional-state)
-(derive :service-unavailable ::exceptional-state)
-
-(defmethod ptk/handle-error ::exceptional-state
-  [error]
-  (ts/schedule
-   (st/emitf (dm/assign-exception error))))
-
-;; We receive a explicit authentication error; this explicitly clears
-;; all profile data and redirect the user to the login page.
-(defmethod ptk/handle-error :authentication
-  [_]
-  (ts/schedule (st/emitf (du/logout))))
-
-;; Error that happens on an active bussines model validation does not
-;; passes an validation (example: profile can't leave a team). From
-;; the user perspective a error flash message should be visualized but
-;; user can continue operate on the application.
-(defmethod ptk/handle-error :validation
-  [error]
-  (ts/schedule
-   (st/emitf
-    (dm/show {:content "Unexpected validation error."
-              :type :error
-              :timeout 3000})))
-
-  ;; Print to the console some debug info.
-  (js/console.group "Validation Error")
-  (ex/ignoring
-   (js/console.info
-    (with-out-str
-      (pprint (dissoc error :explain))))
-   (when-let [explain (:explain error)]
-     (js/console.error explain)))
-  (js/console.groupEnd "Validation Error"))
-
-;; Error on parsing an SVG
-(defmethod ptk/handle-error :svg-parser
-  [_]
-  (ts/schedule
-   (st/emitf
-    (dm/show {:content "SVG is invalid or malformed"
-              :type :error
-              :timeout 3000}))))
-
-;; This is a pure frontend error that can be caused by an active
-;; assertion (assertion that is preserved on production builds). From
-;; the user perspective this should be treated as internal error.
-(defmethod ptk/handle-error :assertion
-  [{:keys [data stack message hint context] :as error}]
-  (let [message (or message hint)
-        context (str/fmt "ns: '%s'\nname: '%s'\nfile: '%s:%s'"
-                              (:ns context)
-                              (:name context)
-                              (str cf/public-uri "js/cljs-runtime/" (:file context))
-                              (:line context))]
-    (ts/schedule
-     (st/emitf
-      (dm/show {:content "Internal error: assertion."
-                :type :error
-                :timeout 3000})
-      (ptk/event ::ev/event
-                 {::ev/type "exception"
-                  ::ev/name "assertion-error"
-                  :message message
-                  :context context
-                  :trace stack})))
-
-    ;; Print to the console some debugging info
-    (js/console.group message)
-    (js/console.info context)
-    (js/console.groupCollapsed "Stack Trace")
-    (js/console.info stack)
-    (js/console.groupEnd "Stack Trace")
-    (js/console.error (with-out-str (expound/printer data)))
-    (js/console.groupEnd message)))
-
-;; This happens when the backed server fails to process the
-;; request. This can be caused by an internal assertion or any other
-;; uncontrolled error.
-(defmethod ptk/handle-error :server-error
-  [{:keys [data hint] :as error}]
-  (let [hint (or hint (:hint data) (:message data))
-        info (with-out-str (pprint (dissoc data :explain)))
-        expl (:explain data)]
-    (ts/schedule
-     (st/emitf
-      (dm/show {:content "Something wrong has happened (on backend)."
-                :type :error
-                :timeout 3000})
-      (ptk/event ::ev/event
-                 {::ev/type "exception"
-                  ::ev/name "server-error"
-                  :hint hint
-                  :info info
-                  :explain expl})))
-
-    (js/console.group "Internal Server Error:")
-    (js/console.error "hint:" hint)
-    (js/console.info info)
-    (when expl (js/console.error expl))
-    (js/console.groupEnd "Internal Server Error:")))
-
-(defmethod ptk/handle-error :default
-  [error]
-  (if (instance? ExceptionInfo error)
-    (ptk/handle-error (ex-data error))
-    (let [stack (.-stack error)
-          hint  (or (ex-message error)
-                    (:hint error)
-                    (:message error))]
-      (ts/schedule
-       (st/emitf
-        (dm/assign-exception error)
-        (ptk/event ::ev/event
-                   {::ev/type "exception"
-                    ::ev/name "unexpected-error"
-                    :message hint
-                    :trace (.-stack error)})))
-
-      (js/console.group "Internal error:")
-      (js/console.log "hint:" hint)
-      (ex/ignoring
-       (js/console.error (clj->js error))
-       (js/console.error "stack:" stack))
-      (js/console.groupEnd "Internal error:"))))
-
-(defonce uncaught-error-handler
-  (letfn [(on-error [event]
-            (ptk/handle-error (unchecked-get event "error"))
-            (.preventDefault ^js event))]
-    (.addEventListener js/window "error" on-error)
-    (fn []
-      (.removeEventListener js/window "error" on-error))))