135 results found
-
Wrong User
I think at the very bottom of this page you meant to write User C because that's what that paragraph is talking about.
2 votes -
Sample code in the Status section is mac only.
Sample code for windows users would be awesome!
2 votes -
If I need Extensions Onboarding, link to it.
You have error messages that tell me I can't do [insert a variety of things here] until I have completed something like "Extensions Monetization Onboarding." The error message fails heuristics because it doesn't let me fix the problem. It says I need to do something but doesn't give me a link or way to do it. That seems like a huge mistake, but with the forums FULL of people complaining that they can't find it either, I'm wondering if it's a dark pattern and done on purpose.
If there is a workflow that requires me to move through certain steps,…
2 votes -
Fix the example GitHub repo to better correlate to the documentation on this page
Provide a link to the referenced branch associated with each step.
There are no branches for steps 3 and 4. The existing branches don't correlate to the code presented for each step on this page.
And there's messy commented out code in all of the files on GitHub.Also, 4 steps are explained, and then the last sentence in this doc mentions the Step 1 branch
2 votes -
Add common (and uncommon) error responses from API request
I received an error I have never seen before and it got me thinking it would be nice to have some documentation on various error messages like "Insufficient authorization in token". Other errors are clear and straight forwards like "missing X scope" however some are vague and unclear.
2 votes -
Improve documentation for WebHooks' hub.secret property
The hub.secret property needs far more explaining of how the secret is generated:
"The X-Hub-Signature header is generated by sha256(secret, notification_bytes)"
It should say something along the lines of
"The X-Hub-Signature header is generated by using HMAC sha256 with the provided secret being the one specified in hub.secret: hmac(sha256, hubsecret).hash(notificationbody)"
2 votes -
Game developer playbook clip not playing
On https://dev.twitch.tv/gamedevelopers/development embedded clip is ot configured properly
2 votes -
Publish Official Typescript Typing's for all Data Models
It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily…
2 votes -
onTransactionComplete trigger result unclear
The use of bullet points reads and the "and" tacked onto the end of the first bullet point makes it unclear
The wording should be revised so it's more obvious that "onTransactionComplete" is to be sent to instances where the userID matches the userID that initiated.
Since the first bullet point is superflous, since the userID of the first bullet point is also matched by the second bullet point.
2 votes -
Please add actual code instead of images in the documentation
Please add actual code instead of images in the documentation. It would be much easier to copy it. Example: https://dev.twitch.tv/docs/tutorials/extension-101-tutorial-series/config-service
2 votes -
VIP scope mistake?
Hey, it says "/vip /unvip" is under "channel:moderate" scope, wouldn't that be moderator status? because I'm sure moderators can't grant/remove VIP status to a user. Or am I wrong?
2 votes -
"Registering your App" an Extension is also an App
https://dev.twitch.tv/docs/authentication
Says
Authentication involves: Registering your app to obtain a client ID and client secret. Getting a token. This includes specifying scopes, the permissions your app requires. Sending the token in your API request, to authenticate API requests.But doesn't mention that an Extension is also an Application
This docs fix would be needed on other pages where "registering an app" is mentioned
2 votes -
Document exact what triggers `viewer.onChanged`
https://dev.twitch.tv/docs/extensions/reference#helper-viewer
SNIPPET STARTS
onChanged
Twitch.ext.viewer.onChanged: void function(callback: Function())This function binds a callback will be invoked when the viewer’s status changes (e.g. if a viewer subscribes and changes their subscription status).
SNIPPET ENDS
Cannot tell if broken or only triggers on subscription status change.
IE is it supposed to trigger on
rolechanges? If so it's bugged, if not the documentation needs to document what does cause onChanged to be called2 votes -
Custom Rewards limit?
Pagination Support
None.
There is a limit of only 50 Custom Rewards on a channel at a time.It's unclear if that means 50 active rewards or 50 total rewards. It should be more plain text/clear.
The help article
https://help.twitch.tv/s/article/making-the-most-of-channel-points?language=en_US
doesn't mentioned this limit either.
2 votes -
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
- Don't see your idea?