143 results found
-
Userstate in IRC is out of date in docs This is out of date. Update it please.
2 votes -
Authentification desctription isn't descriptive enough Description in "Getting tokens" isn't very clear and missing a link to "Getting Tokens: OAuth", where it's all explained in detail. That does confuse people
2 votes -
Complete Response Codes in Twitch Docs It would be great if we could have a list of the status codes and their reasons so we can write code to prepare for handling those errors, instead of logging them and dealing with them as they happen - for all endpoints. These exist, for the most part, in a lot of the newer endpoint documentation, but a lot of the older endpoints were rushed in their documentation and we have little information on what responses to expect. Sometimes we get 200s, 202s, 400s, 410s - and having to just "wait" or try to plan for them is a…
2 votes -
Missing docs on OAuth for initial step by step guide The step by step guide does not reference OAuth tokens yet they are required to do an API request, please update the guide to include info on this.
2 votes -
More information about 'id' uniqueness More information is required about the uniqueness of id. Is it unique forever (i.e. there will never be two messages with the same id) or is it just guaranteed unique within a timeframe?
2 votes -
error in documetation msgid:"usageuntimeout" states:'Usage: “/raid <username>” - Removes a timeout on a user.' and not /untimeout
2 votes -
Add .env files in the Managing Extension Secrets section Another way to manage an extension secret is to use a .env file. The .env file can be used to store all kinds of secrets, tokens, and passwords.
eg: TOKEN=testT0K3N
note: .env is a shell file so there can't be spaces around =
2 votes -
Link to locustfile for load testing extensions not working The formatting of the link to the locustfile in https://dev.twitch.tv/docs/extensions/load-testing-extensions#run-your-locust-test is not working because there are code tags in front of and after:
2 votes -
first extension how-to details Build your first Extension
Here’s an extension that just says ‘Hello, world!’where do i store this? how do i connect this with the twitch extension config page?
2 votes -
Clarify read-only nature of IRC MODE command While you do a good job of stating that the IRC interface deviates from the RFC, as well as where and how it deviates from the RFC, it may be beneficial to specifically call out the deviation that the MODE command is server-generated (read only), instead of being a keyword that can be generated by a client.
In other words, my bot cannot issue its own "MODE #channel +o nickname" command via the IRC interface (like it can on IRC), it can only receive notifications from the server that the server has sett one of those modes. One sentence covering…
2 votesThanks for the head’s up!
-
Missing Scope user:edit:broadcast The Twitch API Scopes list in Authentication is missing the "user:edit:broadcast" scope.
1 vote -
Twitch Extention Document server.py can not be executed because it is written in Python 2x. Also, changing "start": "HTTPS=true PORT=8080 react-scripts start," causes an error. Wouldn't it be better to modify it to write in .env.
1 vote -
****** docs Poorly written docs. Nowhere is mentioned when you would use "Client credentials flow", which EXACT situations. Waste of time.
1 vote -
Undeclared Variable an undeclared variable:
function parseCommand(rawCommandComponent) {
let parsedCommand = null;
commandParts = rawCommandComponent.split(' ');should be "let commandParts = ..."
1 vote -
Ошибка в команде yarn create react-app example-extension
there is a mistake. Command have to beyarn create-react-app example-extension
1 vote -
Error on retrieving hmac message At the full example code, the raw body needs to be passed through the JSON.stringify(<body>) function at the getHmacMessage function since the request is part of the espress.Request class. Or that's what worked for me.
1 vote -
Wrong header in Example request of update redemption status API reference The Example Request in Update Redemption Status API reference contains wrong header. The Client-Id is named as client-id. A small typo error wasted my hour. But yep hopefully it gets fixed for others.
1 vote -
Unclear extensions documentation A few of the elements on the extensions documentation (https://dev.twitch.tv/docs/extensions/reference/) are very confusing, especially in the Bits section. For example:
in getProducts, it looks like
amountandtypeare fields directly in the product object, when they are in fact part of thecostobject within it (the Cost type is not defined anywhere else)in window.Twitch.ext.bits.onTransactionComplete, the
productfield of theTransactionObjectis said to be a string, but its description says "If set to true, will contain “inDevelopment”. Otherwise it return blank". How can it be set to true if it is a string? Also, from…
1 vote -
Tags - Inconsistency between exemple, list and prototype Some part are missing some informations or contain error :
- Private message : send a tags "returning-chatter" that is not explain and not in the prototype of the command.
- Usernotice : you provide an exemple with the tag "msg-param-recipient-name", this tag is not in the list of tags1 vote -
Where is the name listed? "Set Name to your application's name. The name must be unique among all Twitch apps. Your app's name is listed on the Connections page under Other Connections if your app requires user consent to access or modify the user's resources." I do not understand where the name is listed, when I am on the page on which the link sends me there is not that.
1 vote
- Don't see your idea?