Skip to content

fix: preserve explicit null endTime through seek pipeline - #232

Merged
1Lucas1apk merged 1 commit into
PerformanC:devfrom
Akinori107:dev
Sep 5, 2026
Merged

fix: preserve explicit null endTime through seek pipeline#232
1Lucas1apk merged 1 commit into
PerformanC:devfrom
Akinori107:dev

Conversation

@Akinori107

Copy link
Copy Markdown

Changes

seek() now accepts endTime: number | null instead of just number across playerManager.ts, player.ts and both PATCH handlers (sessions.id.groups.ts, sessions.id.players.ts). also stopped collapsing payload.endTime through ?? undefined before it reaches seek()

Why

payload.endTime ?? undefined turned an explicit endTime: null into undefined before it reached seek(), so endTime !== undefined ? endTime : this.track.endTime couldn't tell "clear the end time" apart from "field omitted", silently keeping the old end time instead of clearing it

Checkmarks

  • The modified endpoints have been tested.
  • Used the same indentation as the rest of the project.
  • Still compatible with LavaLink clients.

Additional information

tsc passes. fun fact: lavalink has the same issue, lines here

payload.endTime ?? undefined collapsed an explicit null into undefined before reaching seek(),
so an explicit clear couldn't be told apart from the field being omitted
@1Lucas1apk
1Lucas1apk merged commit a988c62 into PerformanC:dev Sep 5, 2026
1 check passed
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 5, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants