-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for communities #409
Comments
The v3 API version is still being used here, so communities can't be implemented yet... Unfortunately, it's not a simple switch, as all channel/stream endpoints are not referenced by names anymore, but by the twitch-users's id, which requires another API request in most cases. I don't know how much work this will be, since I haven't looked into this yet in detail. The deadline for a v5 switch is mid february 2018. |
The Teams API also needs to be checked again (#93). It looks like they have resolved the issues that prevented an implementation. |
The Twitch v5 API upgrade has just been completed: d4e9885 Cummunities and team pages (and also channel news feeds) can now be implemented. |
I'm not yet 100% convinced by the current implementation of the CommunityItemComponent. |
Okay, looks like the LessCSS compiler is breaking the InfiniteScrollMixin when compressing the stylesheets in the production build because of the identical GameItemComponent and CommunityItemComponent stylesheets. |
The latest feature on twitch is communities https://www.twitch.tv/directory/communities
The feature is still in beta but the API already supports them https://dev.twitch.tv/docs/v5/reference/communities/
The text was updated successfully, but these errors were encountered: