Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ChristopherRotnes merged 1 commit into from
May 4, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions app/api/sportySync.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,15 @@ const SPORTY_BASE_URL =
'https://sporty.no/api/v1/businessunits/8/groupactivities';

function buildSportyUrl(daysAhead = 10) {
const from = new Date().toISOString().slice(0, 10);
const to = new Date(Date.now() + daysAhead * 24 * 60 * 60 * 1000).toISOString().slice(0, 10);
return `${SPORTY_BASE_URL}?from=${from}&to=${to}`;
// sporty.no uses Oslo midnight = previous day T22:00:00.000Z (CEST / UTC+2)
const start = new Date();
start.setUTCHours(22, 0, 0, 0);
start.setUTCDate(start.getUTCDate() - 1);

const end = new Date(start);
end.setUTCDate(end.getUTCDate() + daysAhead);

return `${SPORTY_BASE_URL}?period_start=${encodeURIComponent(start.toISOString())}&period_end=${encodeURIComponent(end.toISOString())}`;
}

function shiftRow(row, shiftMs) {
Expand Down
Loading