Would new feature support be release in the CLI for developers to test against prior to a new feature going live on the Twitch?
Potentially! Given we have control over the implementation in the CLI, we can also test out new features earlier, but that’s TBD.
Very happy to see this.
However: given authentication is one of the most important pieces of the interaction with twitch, one of those that gets a lot of questions, and the thing that you need to make sure you get right, I am of the opinion that leaving it out is a large disservice.
I understand if its not in immediately, but I am in favor of this bloat if it means that I can mock the full auth process without having to hit twitch’s production servers (as I do now).
Mind, having the ability to disable it (just checking, but not validating tokens etc) would be ideal if that is not the component being worked on
Fully agreed with this. For the first iteration, we’re going to offer two options. The first is an online experience whereby we use the production service to validate tokens to avoid fragmentation of mock auth vs. real auth, and the second is the auth-less option.
This way we can allow you to test end-to-end.
If you have specific feedback on what you’d like to see on a mock auth solution, let us know; always happy to look into it. In general, our concern is around user confusion more than anything, especially since it’d be overly simplified vs. the production flows. Just something we’re considering when working through this.