Fix Engagement date filtering (#3350)

The optional matches are not needed, these nodes will always exist. The former clause was causing the filter to not work. Co-authored-by: Carson Full <[email protected]>
SeedCompany · Jan 13, 2025 · 4bcd77b · 4bcd77b
1 parent 52d22cc
commit 4bcd77b
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/components/engagement/engagement.repository.ts b/src/components/engagement/engagement.repository.ts
@@ -733,7 +733,7 @@ export const engagementFilters = filter.define(() => EngagementFilters, {
     node('', 'Language', { id }),
   ]),
   startDate: filter.dateTime(({ query }) => {
-    query.optionalMatch([
+    query.match([
       [
         node('node'),
         relation('out', '', 'startDateOverride', ACTIVE),
@@ -750,7 +750,7 @@ export const engagementFilters = filter.define(() => EngagementFilters, {
     return coalesce('startDateOverride.value', 'mouStart.value');
   }),
   endDate: filter.dateTime(({ query }) => {
-    query.optionalMatch([
+    query.match([
       [
         node('node'),
         relation('out', '', 'endDateOverride', ACTIVE),