fix: undefined values in Likert question matching

Properly returns the `undefined` value instead of a `'undefined'` string if the value is missing.
OpenVAA · Sep 18, 2024 · c1517d4 · c1517d4
1 parent 86281fd
commit c1517d4
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/frontend/src/lib/utils/matching/LikertQuestion.ts b/frontend/src/lib/utils/matching/LikertQuestion.ts
@@ -11,9 +11,9 @@ export class LikertQuestion extends OrdinalQuestion {
     this.category = category;
   }
 
-  normalizeValue(value: number): CoordinateOrMissing {
+  normalizeValue(value: number | undefined): CoordinateOrMissing {
     // The current frontend implemenation of questions uses numbers for choice keys
-    return super.normalizeValue(`${value}`);
+    return super.normalizeValue(Number.isFinite(value) ? `${value}` : undefined);
   }
 }
 /**