Repository navigation
Move Hype Train onto the endpoint that still exists - #8
Merged
Merged
Conversation
Twitch withdrew Get Hype Train Events. hypeTrain->forBroadcaster() has been
failing with 410 in production, and the EventSub hype train types were
still being subscribed at v1, which was withdrawn in the same change.
HypeTrainRepository now targets hypetrain/status:
status($broadcasterId) the {current, all_time_high, shared_all_time_high}
record, or null when the channel has no data
isActive($broadcasterId) whether a train is running right now
status() returns the decoded row rather than a Part. The payload has
nothing in common with HypeTrainEvent, and inventing a Part for a shape
this nested would be guessing at an API that has just changed under us.
forBroadcaster() and latest() are kept as deprecated stubs that reject with
an explanation, so existing callers get a sentence telling them what to do
instead of a bare HTTP 410.
Verified live: status() returns all three documented keys, isActive()
returns false on an idle channel.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Twitch withdrew Get Hype Train Events. hypeTrain->forBroadcaster() has been failing with 410 in production, and the EventSub hype train types were still being subscribed at v1, which was withdrawn in the same change.
HypeTrainRepository now targets hypetrain/status:
status($broadcasterId) the {current, all_time_high, shared_all_time_high}
record, or null when the channel has no data
isActive($broadcasterId) whether a train is running right now
status() returns the decoded row rather than a Part. The payload has nothing in common with HypeTrainEvent, and inventing a Part for a shape this nested would be guessing at an API that has just changed under us.
forBroadcaster() and latest() are kept as deprecated stubs that reject with an explanation, so existing callers get a sentence telling them what to do instead of a bare HTTP 410.
Verified live: status() returns all three documented keys, isActive() returns false on an idle channel.