Skip to content

fix: corrected threshold reset when returning to ongoing season. - #16

Merged
StarsExpress merged 2 commits into
mainfrom
nfl-dev
Oct 27, 2026
Merged

StarsExpress merged 2 commits into
mainfrom
nfl-dev

Conversation

@StarsExpress

Copy link
Copy Markdown
Owner

Auto-adjusted Thresholds

In the past, the season "change" handler only forced a reset for ongoing -> historical.
Reverse direction relied on generic clamp, which fell back to the default only while ongoing season's pool max stayed below the old value.
With 2026 Week 7 data the max (ED 256, DI 244, OL 304) now exceeds 230/300, old values fit and was kept.

Added seasonSwitchChangesThresholdDefault() in data.js:
true when two seasons carry different default_thresholds.

The handler uses it, so both ongoing <-> historical directions reset,
while two finalized seasons — same static default — keep the user's value.

Co-Authored-By: Claude <claude@users.noreply.github.com>
@StarsExpress StarsExpress changed the title fix: ensured threshold truly reset when returning to ongoing season. fix: corrected threshold reset when returning to ongoing season. Oct 27, 2026
Co-Authored-By: Claude <claude@users.noreply.github.com>
@StarsExpress
StarsExpress merged commit fc0d91b into main Oct 27, 2026
3 checks passed
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