fix: handle Eventbrite recurring/series events with nextAvailableSession#226
Merged
fix: handle Eventbrite recurring/series events with nextAvailableSession#226
Conversation
Eventbrite recurring events use a single URL with JSON-LD startDate set to the first occurrence (often past). The pipeline skips these as past events, missing all future occurrences. Detects series events via the embedded isSeries flag and uses nextAvailableSession from the page's goodToKnow.highlights data as the effective start date. This gives the correct upcoming occurrence date without requiring API calls. Tested against: - Monday Night Funk Jam (weekly at Lo-Fi Brewing): startDate now 2026-05-04 - Emerald Empire Band Free Showcase (bi-weekly): startDate now 2026-05-18
Contributor
Homeboy Results —
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Eventbrite recurring events use a single URL with JSON-LD
startDateset to the first occurrence (often past). The pipeline skips these as past events, missing all future occurrences.This PR detects series events via the embedded
isSeriesflag and usesnextAvailableSessionfrom the page'sgoodToKnow.highlightsdata as the effective start date.What changed
extractSeriesMeta()to parseisSeriesandnextAvailableSessionfrom Eventbrite page HTMLparseDates()now overrides startDate/startTime withnextAvailableSessionwhen the event is a seriesTested against
startDatecorrectly resolved to2026-05-04(tomorrow)startDatecorrectly resolved to2026-05-18Both were previously returning past dates and being skipped by the pipeline.