Skip to content

fix #99: use period_start/period_end params for sporty.no date range#100

Merged
ChristopherRotnes merged 1 commit into
masterfrom
fix/99-sporty-period-params
May 4, 2026
Merged

fix #99: use period_start/period_end params for sporty.no date range#100
ChristopherRotnes merged 1 commit into
masterfrom
fix/99-sporty-period-params

Conversation

@ChristopherRotnes
Copy link
Copy Markdown
Owner

Summary

  • Replaces from/to query params with period_start/period_end — the actual parameter names sporty.no uses (confirmed by inspecting live network requests)
  • Switches from date-only strings to full ISO datetimes anchored to Oslo midnight (T22:00:00.000Z, CEST = UTC+2), matching sporty.no's own request format

Test plan

  • Merge and trigger POST /api/sporty-sync
  • GET /api/sporty-health shows latestRow ~10 days ahead of today
  • Verify sync succeeds with 0 new rows when next week's schedule isn't published yet (no error)

🤖 Generated with Claude Code

The API was ignoring from/to — correct parameter names are period_start
and period_end with full ISO datetimes. Anchors to Oslo midnight
(previous day T22:00:00.000Z, CEST=UTC+2) to match sporty.no's own
request format.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ChristopherRotnes ChristopherRotnes merged commit dc1538f into master May 4, 2026
4 of 6 checks passed
@ChristopherRotnes ChristopherRotnes deleted the fix/99-sporty-period-params branch May 4, 2026 14:51
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