143 results found
-
Documentation is misleading The example and/or documentation of the "Channel Points Event Message" seem to be wrong/misleading, because the example reply does not match the structure of "Message Parameters: All Messages"
3 votes -
Modify Channel Information says "Query parameters" example post says JSON blob https://dev.twitch.tv/docs/api/reference#modify-channel-information
The example calls uses JSON, but the documentation talks about Query String/URL encoded form.
Docs should cover both possibilities and examples should cover both methods
3 votes -
Embed documentation doesn't mention the SSL requirment https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL
3 votes -
Fixed position or better visibility for important announcements As per a request from Barry, it would helpful if any flagged messages on a page were fixed or visible when loading a bookmarked section. For example, right now there is an important message on the API reference page about OAuth requirements for Helix, but if someone goes directly to https://dev.twitch.tv/docs/api/reference#get-streams, they will not see this message currently.
3 votes -
Change description of broadcaster_id in create clip The description of the broadcaster_id inside of the Create Clip endpoint is very confusing because it states that this is the id of the stream but it really is the id of the broadcaster as the name suggests.
3 votes -
Enabling Drops This guy does not resemble reality. Part 4: Enabling Drops; Click Your Console ( Where is it, I clicked Your Dashboard); Click Drops ( Where is it? How am I suppose to find it?).
Not approvable3 votes -
Wording on refreshing a token is confusing https://dev.twitch.tv/docs/authentication#refreshing-access-tokens
"
How to Refresh
To refresh a token, you need an access token/refresh token pair coming from a body. For example:
"You need only the "refresh token" and "client secret"
You can lose the access token, and still get a new token if you have a refresh_token
3 votes -
Helper: viewer is misleading as the viewer object is populated on all views not just the channel page https://dev.twitch.tv/docs/extensions/reference#helper-viewer
The Twitch.ext.viewer object is a collection of info about the twitch viewer that is watching the channel page where your extension is activated. It will only be populated if the viewer is logged in, and only after the `onAuthorized` callback has been called. Accessing its properties will otherwise return `null`.Should be
The Twitch.ext.viewer object is a collection of info about the twitch user that is watching the extension view.Or something, as the
viewerhelper object exists on all views!3 votes -
Get Broadcaster Subscriptions docs example incomplete The Get Broadcast Subscriptions docs https://dev.twitch.tv/docs/api/reference#get-broadcaster-subscriptions was updated to include gifterid and giftername fields, but neither of these were added to the example.
Also, the example is erroneous because it shows the same user id for both broadcaster and subscriber, but they represent different usernames, which is impossible.
3 votes -
Document error responses https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow
There's no information about error response and it doesn't seem to be fully compatible with RFC 6749 which means I can't find info about possible errors easily.
3 votes -
Extension popout "by default" From: https://github.com/twitchdev/issues/issues/72
Brief description
By default, pop-out control is enabled for panel Extensions and for extension “live configuration views” (see the Live Config Path setting on the Asset Hosting tab in the Extensions manager).
https://dev.twitch.tv/docs/extensions/required-technical-background
The documentation suggests that extension developers can disable pop-outs. Which is not the case
3 votes -
User/Channel ID needs to be a string From: https://github.com/twitchdev/issues/issues/70
Brief description
The documentation for creating signing JWT's don't explicitly state that
user_id/channel_idin JWT's need to be an explicit string literalhttps://dev.twitch.tv/docs/extensions/building/#signing-the-jwt
https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-messageExpected documentation
Where: exp is the Unix epoch timestamp when the payload will expire. Be sure to provide a buffer, to allow potential positive time drift. user_id is the Twitch user ID that owns the extension, where the user ID is cast as a string literal. role is set to external.3 votes -
Helper: Actions - don't work in the rig From: https://github.com/twitchdev/issues/issues/56
Brief description
Documentation describes that there are functions such as
followChannelandrequestIdSharebut the documentation doesn't mention that these functions don't work in the rig (at time of writing)https://dev.twitch.tv/docs/extensions/reference#helper-actions
Additional context or questions
https://discordapp.com/channels/504015559252377601/523676096277905419/676767529666084864
3 votes -
Information about config service unclear From: https://github.com/twitchdev/issues/issues/55
Brief description
https://dev.twitch.tv/docs/extensions/building#using-the-configuration-service
Doesn't mention the key bit of information regarding the size limit of 5kb
Additional context or questions
It's important to note here as people will start designing an extension and then discover the sizing limit late into construction of an extension. For clarity the limit should be noted here also
3 votes -
onPositionChanged still in docs From: https://github.com/twitchdev/issues/issues/36
Brief description
https://dev.twitch.tv/docs/extensions/reference#helper-extensions
The JS helper/callback function
onPositionChangedis still documented but is no longer relevant post video component redesignExpected documentation
Section Should be removed
3 votes -
How to link out on a mobile extension Twitch documentation does not state how to handle opening a new window on a mobile extension.
3 votes -
Missing Scope user:edit:broadcast The Twitch API Scopes list in Authentication is missing the "user:edit:broadcast" scope.
2 votes -
One language per view After providing feedback. There is the big text "Vielen dank!" I am from germany I appreciate that. But the second line is english. Please stick with one language. This is production environment. People can see that.
2 votes -
Next Step Button Hello guys, I can understand that documentation is boring but it brings a lot benefits on the long term. So please think about those two suggestions:
1) In your 101 tutorials page for example. Add an next page button.
2) Typos are made i know. I do it myself. But before publishing your guide check for typos - its your production environment. people can see this.Cheers
Patrick2 votes -
lickmaballs love you *******
2 votes
- Don't see your idea?