From c3fb3061f6980d451f6592be4307f9ab2f1576c6 Mon Sep 17 00:00:00 2001 From: Carlos Valente Date: Wed, 7 Aug 2024 08:50:10 +0200 Subject: [PATCH] fix: use unfiltered events in timeline --- apps/client/src/features/viewers/timeline/TimelinePage.tsx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/apps/client/src/features/viewers/timeline/TimelinePage.tsx b/apps/client/src/features/viewers/timeline/TimelinePage.tsx index 082090a84..f94a8a9c3 100644 --- a/apps/client/src/features/viewers/timeline/TimelinePage.tsx +++ b/apps/client/src/features/viewers/timeline/TimelinePage.tsx @@ -15,7 +15,6 @@ import style from './TimelinePage.module.scss'; interface TimelinePageProps { backstageEvents: OntimeEvent[]; - events: OntimeEvent[]; general: ProjectData; selectedId: MaybeString; settings: Settings | undefined; @@ -28,14 +27,14 @@ interface TimelinePageProps { * There is little point splitting or memoising top level elements */ export default function TimelinePage(props: TimelinePageProps) { - const { events, general, selectedId, settings, time } = props; + const { backstageEvents, general, selectedId, settings, time } = props; const { getLocalizedString } = useTranslation(); const clock = formatTime(time.clock); const scopedRundown = useMemo(() => { - return getScopedRundown(events, selectedId); - }, [events, selectedId]); + return getScopedRundown(backstageEvents, selectedId); + }, [backstageEvents, selectedId]); const { now, next, followedBy } = useMemo(() => { return getUpcomingEvents(scopedRundown, selectedId);