Closed mjfwebb closed 2 months ago
The recent updates focus on enhancing Twitch integration. Documentation now includes an additional scope requirement for reading moderator followers. In the codebase, the eventSubscribe
function has been updated to accept a version parameter, enhancing flexibility. Additionally, the follow subscription function now includes a moderator user ID and specifies a newer version, aligning with the updated eventSubscribe
function.
File Path | Change Summary |
---|---|
docs/CONFIGURATION.md |
Added moderator:read:followers scope to Twitch requirements |
.../event-sub/subscribers/eventSubscribe.ts |
Added optional version parameter with default '1' |
.../event-sub/subscribers/subscribeToFollows.ts |
Added moderator_user_id and version '2' to parameters |
server/src/handlers/twitch/event-sub/subscribers/subscribeToFollows.ts (1)
`9-17`: Ensure that the `moderator_user_id` is correctly set to the broadcaster's ID as intended.server/src/handlers/twitch/event-sub/subscribers/eventSubscribe.ts (2)
`7-7`: The addition of the `version` parameter with a default value of '1' enhances flexibility in handling different versions of event subscriptions. --- `14-14`: Ensure that the `version` parameter is correctly passed to the API request body.docs/CONFIGURATION.md (1)
`13-13`: The addition of the `moderator:read:followers` scope correctly reflects the updated permissions required by the Twitch API.
The follow event requires an additional scope
moderator:read:followers
and the moderator_user_id to be sent. We use the same value as the broadcaster ID.Summary by CodeRabbit