From afdee911a8b5fe54cb9d26d788fe88726f061ff4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C4=B1nar=20Gen=C3=A7?= Date: Tue, 27 May 2025 15:30:34 +0300 Subject: [PATCH] [fix] Hooks: Added null check for incoming data Problem: - If a filter (custom user property) defined inside the hooks is not exists in the incoming data getting an error. Solution: - Added null check --- CHANGELOG.md | 1 + plugins/hooks/api/parts/triggers/incoming_data.js | 3 +++ 2 files changed, 4 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index d40686b90fe..74e45c962fa 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,7 @@ Enterprise Features: Fixes: - [core] Unifying alphabetical order for dropdowns with dashboard apps +- [hooks] Added null check for incoming data Enterprise Fixes: - [content] Asset URL was wrongly constructed when user switches between apps diff --git a/plugins/hooks/api/parts/triggers/incoming_data.js b/plugins/hooks/api/parts/triggers/incoming_data.js index 7af764b8628..9b157be0b5e 100644 --- a/plugins/hooks/api/parts/triggers/incoming_data.js +++ b/plugins/hooks/api/parts/triggers/incoming_data.js @@ -189,6 +189,9 @@ class IncomingDataTrigger { */ function assertOperation(value, filterObj) { var matched = true; + if (typeof value === 'undefined' || value === null) { + return false; + } if (filterObj.$in && filterObj.$in.indexOf(value) === -1) { matched = false; }