Skip to content

fix: resolve ReferenceError cutoff is not defined in applyFilter#110

Open
Fruhji wants to merge 1 commit into
phuryn:mainfrom
Fruhji:fix/cutoff-not-defined
Open

fix: resolve ReferenceError cutoff is not defined in applyFilter#110
Fruhji wants to merge 1 commit into
phuryn:mainfrom
Fruhji:fix/cutoff-not-defined

Conversation

@Fruhji
Copy link
Copy Markdown

@Fruhji Fruhji commented May 7, 2026

Problem

After opening the dashboard, no data was displayed and the browser console showed:

ReferenceError: cutoff is not defined
    at applyFilter

Root cause

The hourly_by_model filter inside applyFilter() still referenced the old cutoff variable, which was removed when the function was refactored to use { start, end } from getRangeBounds(). All other filters in the same function already used start/end correctly.

Fix

Replace the stale cutoff reference with start and end to match the existing pattern used for filteredDaily and filteredSessions.

The hourly_by_model filter in applyFilter() still referenced the old
"cutoff" variable after the function was refactored to use { start, end }
from getRangeBounds(). This caused a ReferenceError on every filter call,
preventing any data from being displayed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant