Merge pull request #73 from TypingMind/refactor-article-reader

fix(webpage reader): properly handle errors when the api encounters a fetch error
TypingMind · Jan 21, 2025 · a65aa5e · a65aa5e
2 parents 5a4271a + b7ddb20
commit a65aa5e
Showing 1 changed file with 9 additions and 3 deletions.
diff --git a/src/routes/webPageReader/webPageReaderRouter.ts b/src/routes/webPageReader/webPageReaderRouter.ts
@@ -87,11 +87,17 @@ export const webPageReaderRouter: Router = (() => {
         content,
         StatusCodes.OK
       );
-      handleServiceResponse(serviceResponse, res);
+      return handleServiceResponse(serviceResponse, res);
     } catch (error) {
       console.error(`Error fetching content ${(error as Error).message}`);
-      const errorMessage = `Error fetching content $${(error as Error).message}`;
-      return new ServiceResponse(ResponseStatus.Failed, errorMessage, null, StatusCodes.INTERNAL_SERVER_ERROR);
+      const errorMessage = `Error fetching content ${(error as Error).message}`;
+      const serviceResponse = new ServiceResponse(
+        ResponseStatus.Failed,
+        errorMessage,
+        null,
+        StatusCodes.INTERNAL_SERVER_ERROR
+      );
+      return handleServiceResponse(serviceResponse, res);
     }
   });