From eb6e8d0c9341fd0f2c10de2e1a148d48f7c24a2b Mon Sep 17 00:00:00 2001 From: Proddy Date: Sat, 8 Jul 2023 14:10:08 +0200 Subject: [PATCH] comments --- interface/src/AuthenticatedRouting.tsx | 1 - interface/src/api/endpoints.ts | 3 +-- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/interface/src/AuthenticatedRouting.tsx b/interface/src/AuthenticatedRouting.tsx index 0dc0da8b1..3e89334b0 100644 --- a/interface/src/AuthenticatedRouting.tsx +++ b/interface/src/AuthenticatedRouting.tsx @@ -13,7 +13,6 @@ import Security from 'framework/security/Security'; import System from 'framework/system/System'; const AuthenticatedRouting: FC = () => ( - // TODO not sure if this is needed, to redirect on 401. If so add incerceptor to Alova // const location = useLocation(); // const navigate = useNavigate(); // const handleApiResponseError = useCallback( diff --git a/interface/src/api/endpoints.ts b/interface/src/api/endpoints.ts index 4af25b940..ffb1f870e 100644 --- a/interface/src/api/endpoints.ts +++ b/interface/src/api/endpoints.ts @@ -46,8 +46,7 @@ export const alovaInstance = createAlova({ } // Interceptor for request failure. This interceptor will be entered when the request is wrong. - // TODO how best to handle http errors like 401 (unauthorized) - // but I think this is handled correctly in AppRouting? See AuthenticatedRouting() + // http errors like 401 (unauthorized) are handled either in the methods or AuthenticatedRouting() // onError: (error, method) => { // alert(error.message); // }