fix: improve object type handling in normalizeMongoValue and setFieldValue methods

Author: NoOne7135

adminforth/dataConnectors/baseConnector.ts

@@ -236,7 +236,7 @@ export default class AdminForthBaseConnector implements IAdminForthDataSourceCon
       let number: any;
       if (typeof value === "number") {
         number = value;
-      } else if (typeof value === "object" && value !== null) {
+      } else if (typeof value === "object") {
         number = (value as any).valueOf();
       } else {
         number = NaN;
@@ -269,7 +269,7 @@ export default class AdminForthBaseConnector implements IAdminForthDataSourceCon
         throw new Error(`Value is not a decimal. Field ${field.name} got: ${value} (string)`);
       }
 
-      if (typeof value === "object" && value) {
+      if (typeof value === "object") {
         if (typeof value.toString !== "function") {
           throw new Error(`Decimal object has no toString(). Field ${field.name} got: ${String(value)}`);
         }

adminforth/dataConnectors/mongo.ts

@@ -12,7 +12,9 @@ const escapeRegex = (value) => {
 function normalizeMongoValue(v: any) {
   if (v == null) return v;
   if (v instanceof Decimal128) return v.toString();
+  if (v instanceof Double) return v.valueOf();
   if (typeof v === "object" && v.$numberDecimal) return String(v.$numberDecimal);
+  if (typeof v === "object" && v.$numberDouble) return Number(v.$numberDouble);
   return v;
 }