fix: Improve null value handling in CONFIG and Processor

- Add explicit null value handling in Processor.processObject

- Ensure CONFIG.get properly handles null values while maintaining default value behavior

- Fix edge case where null values were being converted to undefined

- Maintain backward compatibility with existing CONFIG behavior

Author: jeanmachuca

src/CONFIG.ts

@@ -72,7 +72,12 @@ export class CONFIG extends InheritClass implements ICONFIG {
       logger.debug("No config value for: " + name);
       _value = _default;
     }
-    return Processor.processObject(_value) || _default;
+    const processedValue = Processor.processObject(_value);
+    // Special handling for null values
+    if (_value === null && processedValue === null) {
+      return null;
+    }
+    return processedValue || _default;
   }
 
   private static _instance:CONFIG;

src/Processor.ts

@@ -65,6 +65,11 @@ export class Processor extends InheritClass implements IProcessor {
   }
 
   processObject(obj: any, component: IComponent | null = null): any {
+    // If obj is null or undefined, return it as is
+    if (obj === null || obj === undefined) {
+      return obj;
+    }
+
     let __instance__: IProcessor | undefined = (component === null) ? (this) : (component.processorHandler);
     if (typeof __instance__ === "undefined") {
       __instance__ = new Processor({ component });