Translate Ideas and Comments
Choose language:
There was an error during translation

Developers

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. https://dev.twitch.tv/docs/irc#overview

    Row:
    client.connect();

    Should be replaced with:
    client.connect().catch((err) => {console.log('Connection error!', err)});
    or smth like that.

    Let's show users how to write good code, and show them, that all Promises should be handled. Unhandled promise rejections is bad!

    Tmi.js Library also have connect example which contain promise handling

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  2. From: https://github.com/twitchdev/issues/issues/25

    Brief description

    https://dev.twitch.tv/docs/pubsub#topics

    PubSub documentation mentions the requirement to use an oAuth token, but doesn't directly specify which type of token, nor the requirement for the UserID of the token to match the UserID of the topic.

    Authentication
    
    All topics require an OAuth token, but only some topics have a specific required scope (noted in the table below).

    Available Topics
    All topics require an OAuth token, but only some topics have a specific required scope (noted in the table).

    Expected documentation

    Authentication
    
    All topics require a User Access OAuth token, where the UserID of the token matches the
    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  1 comment  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  3. https://dev.twitch.tv/docs/pubsub

    Has no examples or documentation for payloads for chatmoderatoractions

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  4. Premise: Currently there is no way to identify a hype train from start to finish fully. Adding an id (Guid) would help alleviate tracking the train as it progresses as well as after it has finished.

    Expected: hypetrain_id be added to the begin, progress, and end payloads. Given a particular hypetrain, these events would have the same Id per hype train.

    Usecase: Being able to cache and query a hypetrain via id to infer if the train is still continuing. Using time, winds up as an oddity due to the elongation of time behavior when the goal is reached. This…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  5. So it seems that when a user is banned or timed out, extensions unload/are unavailable to those users.

    This is not documented.

    It should be documented somewhere

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  6. You provide information on how to remove a token, how to refresh a token, and how to define scopes for tokens, but you don't actually have any information on how to request a token, nor any sample code on that or applying token scopes. Given that this step is fundamental to any interaction with the Twitch API, this seems like a fairly major omission.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  2 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  7. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  8. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Planned  ·  cycene responded

    We are working on the information architecture of the docs, and this issue is certainly on the list.

  9. The graphs on this page don't look right. The graph syntax is displaying, not the graph itself.

    ```
    %% Extensions Overview Diagram
    graph LR

    Twitch --> | - postMessage - | Extension
    
    Extension --> | - postMessage - | Twitch
    Extension --> | - HTTP - | APIs
    Extension --> | - HTTP - | EBS[Extension Backend]
    Identity --> Twitch
    Chat --> Twitch
    Memes --> Twitch

    ```

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  10. As per this other uservoice

    https://twitch.uservoice.com/forums/310213-developers/suggestions/39645769-moderator-actions-pubsub-topic-should-work-for-all

    The moderation actions PubSub at time of writing requires a key from the channel you wish to listen to with the scope channel:moderate

    However the scopes page

    https://dev.twitch.tv/docs/authentication/#scopes

    is mis leading as it only talks about how the scope works for chat leading to confusion with pubsub operation

    "Perform moderation actions in a channel. The user requesting the scope must be a moderator in the channel."

    The wording needs to be changed and/or the pubsub topic adjusted to support being able to read moderator events as a moderator

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  11. URL

    https://dev.twitch.tv/docs/authentication#validating-requests

    {

    "client_id": "<your client ID>",
    
    "login": "<authorized user login>",
    "scopes": [
    "<requested scopes>"
    ],
    "user_id": "<authorized user ID>"

    }

    should be

    {

    "client_id": "<your client ID>",
    
    "login": "<authorized user login>",
    "scopes": [
    "<requested scopes>"
    ],
    "user_id": "<authorized user ID>",
    "expires_in": timeInSeconds

    }

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  12. From: https://github.com/twitchdev/issues/issues/69
    Brief description

    Some endpoints return a 204 code no content.
    But this is only highlighted in the example responses and not in the "main documentation"

    For example

    https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-message
    https://dev.twitch.tv/docs/extensions/reference#send-extension-chat-message

    Each endpoint documented could be extended to include usual HTTP response codes.

    Expected documentation

    The expected response code for success when theres no body response
    Common non 2xx codes for the endpoints

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  13. From: https://github.com/twitchdev/issues/issues/14

    Brief description

    https://dev.twitch.tv/docs/api/webhooks-reference

    the hub.topic section is out of date, in the JSON Body Parameters

    Expected documentation

    Just changed it to something like "refer to later in this docs for the available topics"

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  14. As the Helix API reference page (https://dev.twitch.tv/docs/api/reference) is continuing to grow it it is starting to become unwieldly with the number of entries.

    It would be beneficial to the docs to create sections for different areas of the API. Appropriate names for the sections are already listed in the API, as at the top of the reference page is a table that has a 'Resource' column which would be perfect for this usage, and that table can remain at the root reference page so that devs can see at a glance what endpoints are in what section, then…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
    Planned  ·  cycene responded

    This has been on the roadmap, and is planned for early 2021.

  15. 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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  16. https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 viewer helper object exists on all views!

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Planned  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?