961 results found
-
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 -
copy button for Client-ID Add a copy button for the Client-ID in the dev console for apps.
not urgently needed would just be nice to have
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 -
API for Front page globally It has become difficult to obtain whats on the frontpage by region.
Please provide an API to collect/obtain this data, it's useful for moderation to understand if/why we get a influx of viewers/chatters and can allocate additional bot rules/filters and/or moderation staff
3 votes -
Allow Adobe fonts At the moment, we can only use local fonts or google font in extensions.
I would be great to allow fonts from Adobe to be used too so we can use more fonts for our projects.The css link they give us
<link rel="stylesheet" href="https://use.typekit.net/xxxxxxx.css">or
<style>
@import url("https://use.typekit.net/xxxxxxx.css");
</style>3 votes -
Link to docs from developer console Currently, I find the docs hard to get through, although most documentation is there. It would be nice if you can go to the part of the docs that you might need, at the moment you are having a choice. For example when choosing what type of extension you want, that it will have a link to that specific documentation. Let's say you have chosen Panel, you then get a link to a/some of the example repositories for a Panel, the test channel, and a link to the documentation for creating a Panel.
3 votes -
Allow filtering the JSON API response For example, the YouTube Data API has the "fields parameter" to accomplish this, an example being: items(userid,username,title)
https://developers.google.com/youtube/v3/getting-started#fields
Thanks!
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 -
/helix/moderation/enforcements/status - Return error messages instead of generic 500s When user IDs in the provided data payload do not exists, the endpoint returns a 500 error. Ideally this should return a more detailed error code with an error message related to user IDs.
3 votes -
Issue with v5/bits/extensions/is-eligible/ API There are two scenarios when using this API which return a 500 from the server, but which should return either a 401 or 400 and a meaningful error code to help point out the issue:
If you have set your productSKU's to 'live', but you're testing in 'Hosted testing', you receive this error. A response telling you that you cannot test SKUs in live mode when in hosted testing would be great.
If your extension is live and you are trying to use bits on a channel which doesnt support it, you will receive a 500 from the server. I…
3 votes
- Don't see your idea?