Add WithToken context override for per-request authentication#53
Merged
Its-donkey merged 6 commits intotestfrom Feb 6, 2026
Merged
Add WithToken context override for per-request authentication#53Its-donkey merged 6 commits intotestfrom
Its-donkey merged 6 commits intotestfrom
Conversation
Release v1.1.0: Suspicious user endpoints & changelog monitor
Release v1.1.0
Remove coverage badge auto-commit
Add Jekyll documentation site with custom Twitch-inspired theme
Add GitHub Pages documentation site with custom theme
Allow callers to override the client-level token on a per-request basis using WithToken(ctx, token). This enables concurrent requests with different user tokens through a single client instance, following the same context-override pattern as NoCacheContext.
This was referenced Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
WithToken(ctx, *Token)to allow per-request token overrides via context, enabling concurrent requests with different user tokens through a single client instance.NoCacheContext, checking context token before falling back to the client-levelAuthClientorTokenProvider.Motivation
Endpoints like
Get Channel Followersrequire a user token scoped to each channel (moderator:read:followers). Without per-request token overrides, users must create N separateClientinstances to make concurrent requests for N different channels.WithTokensolves this cleanly:Changes
helix/client.go: AddedWithToken,tokenFromContext,tokenContextKey. ModifieddoOnceWithResponsetoken resolution order (context > authClient > tokenProvider).helix/client_test.go: 5 new tests.