fix: error handling for HTTP status 422

Added error handling for HTTP status 422 in API responses, returning a descriptive QaseError with relevant details.
qase-tms · Nov 26, 2024 · 42890bd · 42890bd
1 parent 65450e1
commit 42890bd
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 2 deletions.
diff --git a/qase-javascript-commons/changelog.md b/qase-javascript-commons/changelog.md
@@ -1,3 +1,9 @@
+# [email protected]
+
+## What's new
+
+Added error handling for HTTP status 422 in API responses, returning a descriptive QaseError with relevant details.
+
 # [email protected]
 
 ## What's new

diff --git a/qase-javascript-commons/package.json b/qase-javascript-commons/package.json
@@ -1,6 +1,6 @@
 {
   "name": "qase-javascript-commons",
-  "version": "2.2.5",
+  "version": "2.2.6",
   "description": "Qase JS Reporters",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

diff --git a/qase-javascript-commons/src/reporters/testops-reporter.ts b/qase-javascript-commons/src/reporters/testops-reporter.ts
@@ -791,7 +791,7 @@ export class TestOpsReporter extends AbstractReporter {
       return new QaseError(message + ': Not found.');
     }
 
-    if (error.response?.status === 400) {
+    if (error.response?.status === 400 || error.response?.status === 422) {
       return new QaseError(message + ': Bad request. Body: \n ' + JSON.stringify(model));
     }