Skip to content

fix(EXLM-5517): Filter out stale upcoming events on Browse all page - #2842

Draft
gauthamksn wants to merge 1 commit into
mainfrom
exlm-5517
Draft

fix(EXLM-5517): Filter out stale upcoming events on Browse all page#2842
gauthamksn wants to merge 1 commit into
mainfrom
exlm-5517

Conversation

@gauthamksn

@gauthamksn gauthamksn commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Please provide the Jira Issue your PR is for.

Jira ID: EXLM-5517

🤖 Auto-generated draft from Jira. Review before marking ready.

What was implemented

The /en/browse page's base Coveo advanced-query (BASE_COVEO_ADVANCED_QUERY) and its Events-V2 counterpart (BASE_COVEO_ADVANCED_QUERY_UPCOMING_EVENT) in scripts/browse-card/browse-cards-constants.js never applied a date check, so events tagged "Upcoming Event" kept showing after they'd already occurred. Both constants now reuse the existing COVEO_UPCOMING_EVENT_STILL_FUTURE_AQ / COVEO_EXCLUDE_STALE_UPCOMING_AQ helpers already relied on by the events-search and atomic-search blocks, so stale upcoming events are excluded consistently everywhere. Only scripts/browse-card/browse-cards-constants.js was touched; npm run lint passes clean.

⚠️ Open Questions / Gaps

  • Headless-browser verification (Playwright) wasn't possible in the sandboxed build environment (missing Chromium shared libraries, and installing system packages was out of scope for an unattended run). Verified instead via lint, node --check syntax validation, and manual boolean-logic verification of the Coveo aq string construction.
  • Per the existing code comment on COVEO_UPCOMING_EVENT_STILL_FUTURE_AQ (EXLM-5361), this date filter only takes effect if the Coveo field el_event_start_time is configured as Date type in the index — if it's still String, >= now is a no-op and stale events will still appear. That's a Coveo-admin/schema change outside this repo's scope; please confirm the field type in production before/after merging.
  • The fix compares against el_event_start_time (event start), matching the pre-existing pattern used by events-search/atomic-search/upcoming-event-v2. A multi-day event that has started but not yet ended would now be excluded once its start time passes. Flagging in case "still in progress" events are expected to remain visible under "Upcoming Events" — that would need a separate end-date comparison.

Test URLs:

AI Review Notes

The Coveo base advanced-query for /en/browse (BASE_COVEO_ADVANCED_QUERY)
and its Events-V2 counterpart (BASE_COVEO_ADVANCED_QUERY_UPCOMING_EVENT)
never applied a date check, so events tagged "Upcoming Event" kept
showing after they'd already occurred. Both now reuse the existing
COVEO_UPCOMING_EVENT_STILL_FUTURE_AQ / COVEO_EXCLUDE_STALE_UPCOMING_AQ
helpers already relied on by the events-search and atomic-search blocks,
so stale upcoming events are excluded consistently everywhere.

Resolves: EXLM-5517
@aem-code-sync

aem-code-sync Bot commented Aug 6, 2026

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run all PSI checks
  • Re-run failed PSI checks
  • Re-sync branch
Commits

@aem-code-sync

aem-code-sync Bot commented Aug 6, 2026

Copy link
Copy Markdown
Page Scores Audits Google
📱 / PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
🖥️ / PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
📱 /en/browse?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
🖥️ /en/browse?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
📱 /en/browse/analytics?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
🖥️ /en/browse/analytics?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
📱 /en/events?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
🖥️ /en/events?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI
📱 /en/search?martech=off Timeout Exceeded PSI
🖥️ /en/search?martech=off PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

1 participant