feat: Refactor EventSub for Hype Train V2 events #242
+59
−42
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.
Breaking
2025‑06‑13
Feature
This pull request updates the
eventsub.go
file to introduce new fields and structures for handling hype train events in a more detailed manner, while also refining existing data types. The most significant changes include the addition of new fields to hype train event structures, the introduction of a new structure for shared train participants, and adjustments to data types for consistency.Updates to hype train event structures:
EventSubHypeTrainBeginEvent
,EventSubHypeTrainProgressEvent
, andEventSubHypeTrainEndEvent
to support version 2 of hype train notifications. These fields includeID
,Level
,Type
,IsSharedTrain
, andSharedTrainParticipants
. RemovedIsGoldenKappaTrain
andLastContribution
fields.Introduction of shared train participant structure:
EventSubSharedTrainParticipant
, to define participants in shared hype trains, including broadcaster details (BroadcasterUserID
,BroadcasterUserLogin
,BroadcasterUserName
).Adjustments to data types:
Total
field inEventSubContribution
fromint64
toint
for consistency.Amount
field toEventSubCharityAmount
for additional granularity in charity-related data.- change fields to match hype train v2