Really cool feature, glad to see this. All of the extensions I have built send a query back to the EBS immediately when they load to get configuration options for the particular channel, those calls will no longer be need when this change rolls out which is great.
I do like having configuration changes propagate to viewers live, but I currently use pubsub broadcasts for that and it’s not a big issue, good to see it’s something you’re considering in the future.
My only real issue is simply with the text that you’re suggesting will be added to the Dev Site in the update. Brevity is good and all, but I’m pretty sure even experienced devs who haven’t built an extension and used the Required Configurations feature before may not be able to easily decipher what option is best suited for their extension, nevertheless non-devs who are trying to have a crack. Why not some actual sentences? For example:
- Will your extension need to store some configuration data for each channel?
- Yes / No radio buttons
Yes leads to:
- Where will you store the channel configuration data?
- Twitch Hosted Config / My EBS
- Does your extension require configuration before it can be used?
- Yes / No
Yes leads to:
- Enter the configuration string for this version of the extensions
- text input
Looking forward to this rollout!